feat: adds method to run workflow for many repos #167
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
owlstronaut
force-pushed
the
owlstronaut/trigger-template-ci
branch
from
4805267 to
28895db
Compare
owlstronaut
force-pushed
the
owlstronaut/trigger-template-ci
branch
from
28895db to
ace94f5
Compare
Contributor
Author
|
Screenshots from run: 
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Oftentimes, the template-oss-apply workflow won't trigger the CI to run on repos. It seems to be a timing thing and can just randomly happen. Rather than trying to run the CI on each repo individually, this will find all npm-cli repos with an indeterminate state and close and reopen them. I wanted to just trigger "CI" to run against each PR, but since it doesn't trigger a
pull_requestaction, it wouldn't actually update the status of the PR. The best way to make it work while allowing the person to still review/merge (so not pushing code and requiring someone else to review) was to just close and reopen the prs.Usage (provided in help text):
npx -p @npmcli/stafftools@latest gh template-oss trigger-ci --table