-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(api/webhook): build approval for fork-no-write #1088
Merged
Merged
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
ecrupper
approved these changes
Mar 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
JordanSussman
approved these changes
Mar 20, 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.
This change resolves an issue with the new build approval feature introduced in
v0.23
:https://github.com/go-vela/community/blob/main/releases/v0.23.md
The issue is builds triggered from a fork by a user with
admin
perms were being forced to wait for an approval.This is unexpected behavior because the repos in question have a build approval policy of
fork-no-write
:https://github.com/go-vela/types/blob/v0.23.2/constants/repo.go#L26-L28
After successfully reproducing the issue locally, I was able to determine the code causing this:
server/api/webhook/post.go
Lines 773 to 786 in 1809638
This code is setup to check if the build sender has access to the repo:
fallthrough
to thefirst-time
approval policycase
statementAfter this change, we'll no longer fallthrough to the
first-time
approval policycase
statement.