chore(ci): switch to bot token for some GitHub Actions workflows #176
Conversation
This file contains 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
Does the PR have any schema changes?Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
|
adding some info: going back to the old workflow of creating an issue before running upgrade-provider will ensure that no duplicate issues or PRs are created |
ocobles
approved these changes
Aug 28, 2024
|
This PR is included in version 0.17.0 🎉 |
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.
GitHub events generated by the built-in, automatic GitHub Actions token are explicitly ignored by GitHub Actions. This means that if an issue or pull request is created with the built-in token, that issue or pull request will not trigger other GitHub Actions workflows.
We previously worked around this issue by switching to scheduled workflows where necessary, but this leads to a large number of duplicate pull requests. Using a custom bot token for the
upgrade-providercommand allows us to roll back the move to scheduled jobs and rely on GitHub events to trigger the necessary workflows on-demand.