Bypass review decision for explicitly requested builds #8095
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
honeyankit
approved these changes
Sep 26, 2023
|
Allowing ourselves to deploying unreviewed PRs, even if only to staging, is something not everybody is comfortable with. I'll test the PR in staging once reviewed. |
deivid-rodriguez
deleted the
deivid-rodriguez/bypass-review-decision-for-explicitly-requested-builds
branch
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.
I'd like to try #8094 in staging, but currently I'd need someone to "dummy-approve" it for me so that the updater images are uploaded. If I do this, the review loses its point.
Would it make sense to not require an approval if I explicitly trigger the workflow to build updater images?