Repository navigation
NO-ISSUE: Let ci-duty force-merge on osac and enhancement-proposals - #269
Conversation
GitHub shows "Merge without waiting for requirements to be met" only to someone who can bypass every rule on the branch. ci-duty bypassed the ci-status-checks ruleset on osac and osac-test-infra, but: - osac's branch protection also requires one approval and a code owner review, which only admins could skip. Add a pull_request_bypassers input to the module and give it to ci-duty on osac. - enhancement-proposals had only managers as a ruleset bypass actor. Add ci-duty. osac-test-infra needs no change: its only rule is the ruleset ci-duty already bypasses. Also remove ItzikEzra-rh from ci-duty. Assisted-by: Claude Code (Claude Opus 5.5) <[email protected]> Signed-off-by: Elior Erez <[email protected]>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe common repository module now supports pull-request bypassers. The osac and enhancement-proposals settings add ci-duty to their bypass configuration, and the README describes the updated scope. ChangesRepository bypass configuration
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Suggested labels: Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check | Check skipped - CodeRabbit’s high-level summary is enabled. | |
| Title check | The title clearly and concisely describes the main change: allowing ci-duty to force-merge on osac and enhancement-proposals. | |
| Docstring Coverage | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… | |
| Linked Issues check | Check skipped because no linked issues were found for this pull request. | |
| Out of Scope Changes check | Check skipped because no linked issues were found for this pull request. | |
| No-Hardcoded-Secrets | The pull request adds Terraform configuration, team names, documentation, and a membership removal. The added values contain no API keys, tokens, passwords, private-key material, embedded URL credenti… | |
| No-Weak-Crypto | The authoritative PR diff changes Terraform GitHub bypass configuration, CSV membership, and documentation. A targeted scan of added lines found no weak-crypto terms or secret/token comparisons; repos… | |
| No-Injection-Vectors | PASS: The pull request changes only Terraform configuration, CSV membership data, and documentation. The added Terraform passes a list of repository review bypasser names and team IDs; it does not add… | |
| Container-Privileges | PASS: The PR changes Terraform, CSV, and README files only. It adds no container or Kubernetes manifest and no privileged, host namespace, SYS_ADMIN, or allowPrivilegeEscalation setting. |
|
| No-Sensitive-Data-In-Logs | No changed code adds logging or emits passwords, tokens, API keys, PII, session IDs, or customer data. The pull request only changes Terraform configuration, team membership, and documentation. Existi… | |
| Ai-Attribution | AI use is disclosed in the PR and commit. The single commit includes the Red Hat Assisted-by: Claude Code (Claude Opus 5.5) <[email protected]> trailer. No Co-Authored-By trailer appears. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)
Full details: No-Hardcoded-Secrets
-
Explanation
The pull request adds Terraform configuration, team names, documentation, and a membership removal. The added values contain no API keys, tokens, passwords, private-key material, embedded URL credentials, or base64/hex blobs over 32 characters. The README mentions credential environment variables and GitHub tokens only as documentation, not as assigned string literals.
Full details: No-Weak-Crypto
-
Explanation
The authoritative PR diff changes Terraform GitHub bypass configuration, CSV membership, and documentation. A targeted scan of added lines found no weak-crypto terms or secret/token comparisons; repository matches are ordinary descriptions and configuration labels, not cryptographic code. No MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or non-constant-time secret comparison was introduced.
Full details: No-Injection-Vectors
-
Explanation
PASS: The pull request changes only Terraform configuration, CSV membership data, and documentation. The added Terraform passes a list of repository review bypasser names and team IDs; it does not add SQL, shell execution, eval/exec, deserialization, unsafe YAML loading, or HTML injection.
Full details: No-Sensitive-Data-In-Logs
-
Explanation
No changed code adds logging or emits passwords, tokens, API keys, PII, session IDs, or customer data. The pull request only changes Terraform configuration, team membership, and documentation. Existing credential references in README and workflow files are unchanged and are not logging behavior.
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
Comment @coderabbitai help to get the list of available commands.
Summary
Since #268,
ci-dutymembers don't see GitHub's "Merge without waiting for requirements to be met (bypass rules)" checkbox on osac. GitHub shows it only to someone who can bypass every rule on the branch:osacrequired_approvals = 1,require_code_owner_reviews = true). Only admins could skip it; before #268 the force-merge group were admins throughwg-infra.pull_request_bypassers, set toosac-project/ci-dutyon osac.osac-test-infraci-status-checksruleset, whichci-dutyalready bypasses.enhancement-proposalsci-dutywasn't a bypass actor on itsci-status-checksruleset.ci-dutytoruleset_bypass_team_ids.Also removes
ItzikEzra-rhfromci-duty.Changes
modules/common_repository: newpull_request_bypassersvariable (default[]), passed torequired_pull_request_reviews.pull_request_bypassers. No effect on repos that don't set it.repositories.tf: on osac,pull_request_bypassers = ["osac-project/ci-duty"]; on enhancement-proposals,ci-dutyis added to the ruleset bypass list.team-members/ci-duty.csv:ItzikEzra-rhis removed. They keep push on all repos throughwg-qe.teams.csv(ci-duty description) andREADME.md: describe the force-merge scope.Validation
tofu fmt -check -recursive,tofu validate,pre-commit run --all-files: pass.module.repo_osac.github_branch_protection.repo_protection[0]andmodule.repo_enhancement_proposals.github_repository_ruleset.status_checks[0], theci-dutydescription, and the 2 recurring repo updates; 1 destroy (ItzikEzra-rh's ci-duty membership). I'll post the local plan output once it's run.ci-dutymember who isn't an org owner sees the bypass checkbox on an osac PR and on an enhancement-proposals PR.🤖 Generated with Claude Code
Summary
ci-dutyas a ruleset bypass team onenhancement-proposals. Onosac, adds the team as a pull-request review bypasser as well as a ruleset bypass actor. The README documents that the bypass can skip merge-queue, status-check, and—onosac—required-review rules.pull_request_bypassersinput tomodules/common_repository. It defaults to an empty list, so callers that do not set it retain the existing behavior.ItzikEzra-rhfrom theci-dutymember list. The supplied objective states that they retain push access throughwg-qe.ci-dutyteam description. No database, controller, or deployment changes are shown. No test changes are included. The author reports thattofu fmt -check -recursive,tofu validate, andpre-commit run --all-filespass; these results were not independently verified.Compatibility
The new module input is backward-compatible for existing callers because it defaults to
[]. The repository rules change expandsci-dutymembers’ ability to bypass merge requirements. Removing a member changes that person’sci-dutyaccess.Risk classification
Unavailable. The supplied evidence does not include the labeling instructions, an applied risk label, or the criteria for
risk:ship,risk:show, andrisk:ask. The evidence also does not support determining whether the change was close to another classification.