use autoupdate/release-1.xx-strict branches for strict
#411
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
|
|
Can you link to the failing auto update jobs? Is there anyway to adjust the branch-protection rules instead? |
|
An example can be seen in https://github.com/canonical/k8s-snap/actions/runs/8986030620/job/24681222255#step:4:5, where the job currently succeeds precisely because of manually bypassing the branch protection rules. |
neoaggelos
added a commit
that referenced
this pull request
May 9, 2024
* use autoupdate/release-1.xx-strict branches for strict * adjust CI branches
neoaggelos
added a commit
that referenced
this pull request
May 9, 2024
* use autoupdate/release-1.xx-strict branches for strict * adjust CI branches
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.
Summary
Use
autoupdate/release-1.xx-strictfor strict release branches, to avoid having the auto promotion jobs failing due to branch protection rulesThis also makes the strict branches fall in line with
autoupdate/strict, to make it clear that these branches are not to be interacted with.