Skip to content

Remove GitHub ruleset from enhancement-proposals repo - #238

Merged
minmzzhang merged 1 commit into
osac-project:mainfrom
redhat-chai-bot:remove-enhancement-proposals-ruleset
Sep 29, 2026
Merged

minmzzhang merged 1 commit into
osac-project:mainfrom
redhat-chai-bot:remove-enhancement-proposals-ruleset

Conversation

@redhat-chai-bot

Copy link
Copy Markdown
Contributor

Drop the native GitHub required_status_checks (check-human-reviews, pre-commit) and ruleset_bypass_team_ids from the enhancement-proposals repository module. Set required_approvals to null since Prow plugins handle approval via OWNERS files (lgtm/approved labels) instead of native GitHub reviews.

This aligns enhancement-proposals with the Prow/Tide merge automation pattern already used by the osac mono-repo.

Context

The enhancement-proposals repo had a GitHub branch protection ruleset requiring 2 native GitHub "Approve" reviews, which conflicted with the Prow-based approval workflow. PRs with all required Prow labels (lgtm, approved, jira/valid-reference) and green CI were blocked because Prow's /lgtm adds a label but does not submit a native GitHub approval review.

Per team decision, enhancement-proposals should be managed solely by Prow — no merge queue and no GitHub ruleset.

Changes

  • required_approvals: 2 → null (Prow labels handle approvals)
  • required_status_checks: removed (check-human-reviews, pre-commit)
  • ruleset_bypass_team_ids: removed (no ruleset to bypass)

Basic branch protection is preserved (linear history, no force push, PRs required).


AI-generated. Review for accuracy.

@minmzzhang requested in Slack thread

Drop the native GitHub required_status_checks (check-human-reviews,
pre-commit) and ruleset_bypass_team_ids from the enhancement-proposals
repository module. Set required_approvals to null since Prow plugins
now handle approval via OWNERS files (lgtm/approved labels) instead of
native GitHub reviews.

This aligns enhancement-proposals with the Prow/Tide merge automation
pattern already used by the osac mono-repo.

AI-Assisted-By: Chai Bot (osac_public persona)
Signed-off-by: Chai Bot <chai-bot@redhat.com>
@coderabbitai

coderabbitai Bot commented Sep 29, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 89987d3d-1b94-4041-8535-8b85defb9710


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

@minmzzhang
minmzzhang merged commit 3383907 into osac-project:main Sep 29, 2026
2 checks passed
minmzzhang pushed a commit that referenced this pull request Sep 29, 2026
)

Restores the `required_status_checks` and `ruleset_bypass_team_ids` for
the `enhancement-proposals` repository that were removed in PR #238.

PR #238 correctly set `required_approvals` from `2` to `null` (letting
Prow handle approvals via labels), but also removed the CI status
checks. Per reviewer feedback, the status checks should remain as hard
gates.

## Changes

- Restores `required_status_checks` with `check-human-reviews` and
`pre-commit`
- Restores `ruleset_bypass_team_ids` for `wg-infra`
- `required_approvals` stays at `null` (from PR #238)

## Net effect from original config

The only difference from the original configuration is
`required_approvals: 2 → null`. All other settings are restored to their
original values.

---
*AI-generated. Review for accuracy.*

@minmzzhang requested in [Slack
thread](https://redhat-internal.slack.com/archives/C0B8KR3HK16/p1790608924340709)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary
- Restores `check-human-reviews` and `pre-commit` as required status
checks for `enhancement-proposals`, each with integration ID `15368`.
- Restores the `wg-infra` team’s ruleset bypass.
- Keeps `required_approvals = null`.

## Affected areas
- **Repository configuration:** Updates GitHub ruleset settings in
`repositories.tf`.
- **CI and access control:** Requires the two checks and allows
`wg-infra` to bypass the ruleset.
- **API, controllers, database, tests, and documentation:** No changes
reported.
- **Backward compatibility:** No API or data compatibility change is
reported. The merge rules change: both checks must pass for merges
unless the ruleset is bypassed.

Tests are not reported.

## Risk classification
No `risk:ship`, `risk:show`, or `risk:ask` label can be substantiated.
The supplied context and repository search do not provide classification
criteria or an applied label. The evidence is insufficient to identify a
nearby classification or explain why it did not qualify.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Chai Bot <chai-bot@redhat.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.

3 participants