Repository navigation
feat(gatekeeper): add optional exempt_paths input #55
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
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.
When an
exempt_pathsPR spans more than one GitHub API page, this jq invocation processes eachgh api --paginatepage as a separate JSON array/object (the GitHub CLI docs for--paginatesay to use--slurpto wrap all pages). An all-exempt changeset then setsEXEMPTto multiple lines such astrue\ntrue, so the later[ "$EXEMPT" = "true" ]check fails and the bot PR still requires two approvals. This breaks the new exemption for large generated/app-only updates; slurp and flatten the paginated pages before applyingall(...).Useful? React with 👍 / 👎.
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, but I believe this is a false positive.
gh api --paginatealready merges JSON-array responses into a single array, sojqruns once andEXEMPTis a single value —--slurpdoes the opposite (it nests pages into an array-of-pages).Verified empirically against a 14-item array forced into 7 pages:
If pages were emitted separately, that would print
2seven times; insteadjqsees one merged array of 14. The pre-existing docs-only exemption already relies on this same auto-merge, and this PR doesn't change thegh api --paginatefetch. So no change is needed here.