Skip to content

Commit 69b8c24

Browse files
committed
Change publish to true in zenodraft action and update README.dev.md
1 parent 3bfb6c7 commit 69b8c24

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

.github/workflows/zenodraft.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ jobs:
2121
with:
2222
collection: 1404735
2323
metadata: .zenodo.json
24-
publish: false
24+
publish: true
2525
sandbox: false
2626
upsert-doi: true
2727
upsert-location: identifiers[0]

README.dev.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,7 @@ This section describes how to make a release in 2 parts:
184184
1. Check that the [Publish](https://github.com/citation-file-format/cff-initializer-javascript/actions/workflows/publish.yml) workflow was triggered by making the release, and that it was successful.
185185
1. Inspect the deployed github.io website [https://citation-file-format.github.io/cff-initializer-javascript/](https://citation-file-format.github.io/cff-initializer-javascript/).
186186
1. Check whether the [zenodraft](https://github.com/citation-file-format/cff-initializer-javascript/actions/workflows/zenodraft.yml) workflow was triggered correctly when the GitHub release was created.
187-
1. Go to Zenodo, log in, inspect the draft release. If all looks good, click "Publish" in Zenodo's frontend.
187+
1. Go to Zenodo and verify that the new DOI was created by zenodraft.
188188

189189
## References
190190

0 commit comments

Comments
 (0)