Adding zenodraft action #440
Draft
+264
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
✅ Deploy Preview for nlesc-guide-testing ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for nlesc-guide-testing ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
ALL contributions
python3 -m http.server 4000and confirmed they work correctly.docker run --init -it -v `pwd`:/docs lycheeverse/lychee /docs --config=docs/lychee.toml, at least for the files I changed.CITATION.cfffile.