💥 require token for creating pull requests in auto update #8
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
burgholzer
added
continuous integration
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.
This PR adapts the reusable auto-update workflow for mqt-core to require a token for creating the update PR.
Ideally, this token is a Personal Access Token with
reposcope because this allows the creation of the PR to also trigger correspondingon: pull requestworkflows in the PR.Alternatively, the regular
{{ github.token }}can be used, which still allows to create PRs, but workflows will not be run automatically for the created PR.In order to still run workflows for such PRs, the PR can be manually closed and re-opened, which explicitly triggers the workflow runs.