Skip to content

Commit 4464d10

Browse files
abelsiqueirac-martinez
authored andcommitted
Allow triggering zenodraft manually for when the action is not triggered
1 parent 4fd4d27 commit 4464d10

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

.github/workflows/zenodraft.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ on:
44
release:
55
types:
66
- published
7+
workflow_dispatch:
78

89
jobs:
910
publish:

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. Verify that the [Preview](https://github.com/citation-file-format/cff-initializer-javascript/actions/workflows/preview.yml) workflow was triggered on release deploying a preview of the tag to <https://cffinit.netlify.com/TAG>.
187-
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. 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. If it was not, then trigger it manually.
188188
1. Go to Zenodo and verify that the new DOI was created by zenodraft.
189189

190190
## References

0 commit comments

Comments
 (0)