Skip to content

fix(pr-quality): require last push approval — align codified ruleset with org policy (#575)#582

Merged
don-petry merged 1 commit into
chore/relocate-rulesets-575from
fix/pr-quality-require-last-push-approval
Jul 2, 2026
Merged

fix(pr-quality): require last push approval — align codified ruleset with org policy (#575)#582
don-petry merged 1 commit into
chore/relocate-rulesets-575from
fix/pr-quality-require-last-push-approval

Conversation

@don-petry

Copy link
Copy Markdown
Contributor

Summary

Sets require_last_push_approval: true in the codified standards/rulesets/pr-quality.json. Answers the review question on petry-projects/.github-private#1013: there is no good reason for it to be false — it was baked in at authoring time (#972), and the org's actual policy is true.

Evidence

Live require_last_push_approval across the fleet is split (drift):

true false
.github, .github-private, TalkTerm, google-app-scripts ContentTwin, markets, broodly
  • The meta-repos and newer repos already enforce true — that's the intended policy.
  • #895 verified auto-rebase's update-branch is exempt from require_last_push_approval (and dismiss-stale), so enabling it does not fight the auto-rebase flow — the historical worry that would justify false.

Blast radius

On the next apply-rulesets.sh run this tightens the three drifted repos still at false (ContentTwin, markets, broodly) and is a no-op on the four already at true. The applier is operator-invoked, so this takes effect deliberately, not automatically.

Notes

Part of #575.

🤖 Generated with Claude Code

…with org policy (#575)

The codified pr-quality had require_last_push_approval=false, baked in when the file
was authored (#972). That contradicts the org's actual policy: the meta-repos
(.github, .github-private) and newer repos (TalkTerm, google-app-scripts) already
enforce require_last_push_approval=true live, and #895 verified auto-rebase's
update-branch is EXEMPT from last-push-approval (so enabling it does not fight the
auto-rebase flow). Set the codified source of truth to true.

Blast radius on next apply-rulesets run: tightens the three drifted repos still at
false (ContentTwin, markets, broodly); no-op on the four already at true.

Stacked on #577 (the relocation). Resolves the pr-quality file-vs-live drift flagged
in petry-projects/.github-private#1013.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 2, 2026 22:34
@don-petry
don-petry requested a review from a team as a code owner July 2, 2026 22:34
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c77b95df-62fb-4280-a69b-988d07d5502f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/pr-quality-require-last-push-approval

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the pull request quality ruleset configuration in standards/rulesets/pr-quality.json to enable the require_last_push_approval setting. There are no review comments, and I have no additional feedback to provide.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 0
- No actionable code review issues found
Files changed: None (PR is approved as-is)
Skipped (informational): 1 (Codex limit message is system error, not a code finding)
```
The PR is ready to merge pending CI completion.

@don-petry
don-petry merged commit 0dc0f02 into chore/relocate-rulesets-575 Jul 2, 2026
8 of 10 checks passed
@don-petry
don-petry deleted the fix/pr-quality-require-last-push-approval branch July 2, 2026 22:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Aligns the codified pr-quality ruleset definition with the organization’s intended policy by enabling “require last push approval” in standards/rulesets/pr-quality.json.

Changes:

  • Set require_last_push_approval to true in the pr-quality ruleset JSON.

"required_review_thread_resolution": true,
"dismiss_stale_reviews_on_push": true,
"require_last_push_approval": false,
"require_last_push_approval": true,
don-petry added a commit that referenced this pull request Jul 2, 2026
…sets/ (#575) (#577)

* chore(rulesets): relocate code-quality + pr-quality JSON to standards/rulesets/ (#575)

Move the org-wide compliance ruleset source of truth into its canonical home in
petry-projects/.github. `.github` owns org-wide standards and compliance policy;
`.github-private` is scoped to agents/skills and their assets (repo boundary
codified in #576).

- Add standards/rulesets/{code-quality,pr-quality}.json — byte-identical to the
  current .github-private/.github/rulesets/ copies (the 4-check code-quality set;
  NO coverage/secret-scan additions, which are sequenced separately to avoid
  bricking fleet repos that don't yet produce those checks).
- Add standards/rulesets/README.md documenting source-of-truth, the scope
  boundary (release-channel-tags stays in .github-private), and the safe-sequencing
  rule for required-check additions.
- github-settings.md: add a "Source of truth" pointer to standards/rulesets/.
- AGENTS.md: add a Rulesets row to the Organization Standards index.

The tooling repoint (apply-rulesets.sh + bootstrap-new-repo.sh) and removal of the
JSONs from .github-private land in a follow-up PR against .github-private, which
must merge after this one.

Part of #575. Follows #576.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(pr-quality): require last push approval — align codified ruleset with org policy (#575) (#582)

The codified pr-quality had require_last_push_approval=false, baked in when the file
was authored (#972). That contradicts the org's actual policy: the meta-repos
(.github, .github-private) and newer repos (TalkTerm, google-app-scripts) already
enforce require_last_push_approval=true live, and #895 verified auto-rebase's
update-branch is EXEMPT from last-push-approval (so enabling it does not fight the
auto-rebase flow). Set the codified source of truth to true.

Blast radius on next apply-rulesets run: tightens the three drifted repos still at
false (ContentTwin, markets, broodly); no-op on the four already at true.

Stacked on #577 (the relocation). Resolves the pr-quality file-vs-live drift flagged
in petry-projects/.github-private#1013.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore: dev-lead update (review-changes) [skip ci-relay]

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com>
Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants