fix(app-autoscaler-release): allow admins to bypass required status checks #813
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
geigerj0
changed the title
silvestre
approved these changes
Apr 17, 2024
|
I'm not aware of any other solution than disabling branch protection for admins. |
stephanme
approved these changes
Apr 17, 2024
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.
Problem
The release pipeline of
app-autoscaler-releaseis broken because the CI-user is no longer allowed to push directly tomainsince all required status checks must pass.remote: error: GH006: Protected branch update failed for refs/heads/main. remote: error: Changes must be made through a pull request. 11 of 11 required status checks are expected.https://concourse.app-runtime-interfaces.ci.cloudfoundry.org/teams/app-autoscaler/pipelines/app-autoscaler-release/jobs/release/builds/30#L65f9ea50:12:13
The problem is more or less the same as this here #674.
Solution
Allow admins to bypass the required status checks