Workflow for Automating PR Creation for Release Updates #112
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
slashpai
reviewed
Oct 25, 2024
|
Discussed this today, some plans for testing:
|
| name: Check and Update Release Version | ||
|
|
||
| on: | ||
| schedule: |
There was a problem hiding this comment.
this would enable to trigger the workflow manually (and not wait for the cronjob).
Suggested change
| schedule: | |
| workflow_dispatch: | |
| schedule: |
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.
Closes prometheus-operator/prometheus-operator#6877. With this workflow, a PR will be automatically created when the upstream release in prometheus-operator repository does not match the release version in https://github.com/prometheus-operator/website/blob/main/data/prometheusOperator.json.