Adding zenodraft action

[c-martinez]

Changes in this PR

Adds GitHub action for publishing Guide as PDF in Zenodo using Zenodraft workflow.
Related to #270

One thing I am not sure is how to configure the action so that it can be manually tested on Zenodo Sandbox, and publishes to Zenodo on releases. The action would require two separate concept DOIs, but it looks like only one can be given. Any suggestions?

Checklist

Most check items are not relevant for this PR since it does not modify the content of the guide, but the publishing infrastructure.

SIGNIFICANT changes / additions, e.g. new chapters

• I checked whether the contribution fits in The Turing Way before considering contributing to this Guide.
• I discussed my contribution in an issue and took into account feedback.

ALL contributions

• I previewed my changes locally using e.g. python3 -m http.server 4000 and confirmed they work correctly.
• I checked for broken links, e.g. using the link checker GitHub Action workflow, or locally by using docker run --init -it -v `pwd`:/docs lycheeverse/lychee /docs --config=docs/lychee.toml, at least for the files I changed.
• My name was added to the CITATION.cff file.

[netlify]

✅ Deploy Preview for nlesc-guide-testing ready!

Name	Link
🔨 Latest commit	3e6ee60
🔍 Latest deploy log	https://app.netlify.com/sites/nlesc-guide-testing/deploys/68191557af076100086f9021
😎 Deploy Preview	https://deploy-preview-440--nlesc-guide-testing.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[netlify]

✅ Deploy Preview for nlesc-guide-testing ready!

Name	Link
🔨 Latest commit	16017d1
🔍 Latest deploy log	https://app.netlify.com/projects/nlesc-guide-testing/deploys/685a762e1e942e0008c382eb
😎 Deploy Preview	https://deploy-preview-440--nlesc-guide-testing.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[bouweandela]

I believe Zenodo is able to read CITATION.cff files, so adding the same information in a .zenodo.json file may not be necessary.

One thing I am not sure is how to configure the action so that it can be manually tested on Zenodo Sandbox, and publishes to Zenodo on releases. The action would require two separate concept DOIs, but it looks like only one can be given. Any suggestions?

would adding two copies of the action file work? With the only difference the DOI?

[egpbos]

We discussed follow-up edits: copy the last step and trigger that one and the draft one before conditionally: edit the last one for tagged releases (published) and keep the other one for drafts/tests, triggering manually with workflow_dispatch.

[egpbos]

Just FYI: the published action actually also triggers for pre-releases, which might feel a bit counterintuitive (it does to me). The reason we must use it instead of the released action (which is triggered when the actual release is made final) is that zenodraft only supports the published and the workflow_dispatch actions.

[egpbos]

Note: the branch was outdated, so did a rebase on main. If you want to continue working on the latest branch on your laptop, do a git pull --rebase.

[egpbos]

We cannot test this from within the PR, so I'm going to merge this now.

[egpbos]

Abusing my power to avoid our branch protection rules, muahaha!