Build the current docs on master too

[ewels]

Now that we're automating the build of the docs, I figure we can show the latest development docs off master too.

Updated the website build to trigger a nightly build to make sure that they're always up to date.

[netlify]

✅ Deploy Preview for nextflow-staging ready!

Name	Link
🔨 Latest commit	fb76c57
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-staging/deploys/65fd9a2fbc07ff00084c4d34
😎 Deploy Preview	https://deploy-preview-184--nextflow-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 70 (🔴 down 10 from production) Accessibility: 80 (no change from production) Best Practices: 92 (no change from production) SEO: 77 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pditommaso]

Where is this going to be pushed?

[ewels]

Where is this going to be pushed?

It's extending the current publishing system that was merged in the Astro rewrite:

1. GitHub action fires (push, cron etc)
2. Action runs the npm run build command
3. This command does type checking on the website and runs the website static build, then runs the build_docs.sh script
4. The build_docs.sh script is the one modified in this PR. It clones the Nextflow repo, checks out the relevant tags / branches, builds the docs and adds them on top of the built static astro website.
5. The action goes on to run make publish and make invalidate
6. Makefile pushes to cloudflare and then invalidates cloudflare cache

A bit convoluted, I set it up this way to try to make the process as familiar as possible 😅 e.g. it uses the exact same makefile commands as before for publishing.

[ewels]

So sorry, TLDR - it'll be published at https://nextflow.io/docs/dev

[pditommaso]

So sorry, TLDR

😆

Should we do https://www.nextflow.io/docs/master/ for consistency with the branch name?

[bentsherman]

I think we should rename latest to stable. All three of these docs builds are the "latest" in a certain sense -- latest stable, latest edge, latest master -- and I think this is confusing for people

[ewels]

Happy to do master - if you're sure that you're not going to rename to main any time soon? 😅

@bentsherman I had thought the same, but I'm not keen on changing the URL at the moment as there are so many links out in the wild pointing to it. Not sure that the reward is worth the change.

[ewels]

Should we do https://www.nextflow.io/docs/master/ for consistency with the branch name?

Done ✅