Skip to content

ci: require code owner review - #29

Merged
kriptoburak merged 2 commits into
mainfrom
codex/add-codeowners
Jul 30, 2026
Merged

ci: require code owner review#29
kriptoburak merged 2 commits into
mainfrom
codex/add-codeowners

Conversation

@kriptoburak

@kriptoburak kriptoburak commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • assign every path to two maintainers with write permission
  • activate the protected branch's required code-owner review
  • strengthen future review evidence without increasing approvals beyond the available independent reviewer count

Validation

  • verified both listed owners have write permission
  • enabled required code-owner review while preserving stale-review dismissal and last-push approval
  • git diff --check

Note

Require code owner review for all repository paths

Adds CODEOWNERS mapping all paths (*) to @kriptoburak and @furkanerday, so GitHub enforces their review approval on every pull request.

Macroscope summarized a82218a.

@kriptoburak
kriptoburak requested a review from furkanerday July 28, 2026 16:52
@kriptoburak
kriptoburak enabled auto-merge (squash) July 28, 2026 16:52

@furkanerday furkanerday left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Reviewed the complete diff, description, commit history, checks, discussion, repository policy, relevant contracts, tests, dependency and release integrity, licensing, and public-safety implications. Required checks are green and no actionable review threads remain.

@furkanerday furkanerday left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Human-authored commits bc04db3, 0dc25b0 lack author-matching Signed-off-by trailers. Each author must amend their own affected commit and re-push it; a later maintainer commit cannot cure an earlier contributor commit. Re-request review after the rewritten commit history and required checks complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 1 file

Re-trigger cubic

@kriptoburak

Copy link
Copy Markdown
Member Author

Rewrote the PR commits without changing the patch to add exact author-matching DCO trailers, and rebased onto the current base branch. Fresh hosted checks can now validate the rewritten history.

@kriptoburak
kriptoburak force-pushed the codex/add-codeowners branch from 0dc25b0 to a82218a Compare July 30, 2026 16:01
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kriptoburak, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: eee25513-e73a-4983-b858-658e42c593f1

📥 Commits

Reviewing files that changed from the base of the PR and between e58c595 and a82218a.

📒 Files selected for processing (1)
  • .github/CODEOWNERS

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

@kriptoburak
kriptoburak requested a review from furkanerday July 30, 2026 16:11
@kriptoburak
kriptoburak dismissed furkanerday’s stale review July 30, 2026 16:15

Dismissed after verifying every affected commit on the current head has an exact author-matching Signed-off-by trailer. Independent re-review remains requested.

@furkanerday furkanerday left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Reviewed the complete current diff, description, commit history, checks, discussion, repository policy, relevant contracts and tests, dependency and release integrity, licensing, DCO, and public-safety implications. Required checks are green and no actionable review threads remain.

@kriptoburak
kriptoburak merged commit 7d3f88c into main Jul 30, 2026
17 checks passed

@furkanerday furkanerday left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Reviewed the complete current diff, description, commit history, checks, discussion, repository policy, relevant contracts and tests, dependency and release integrity, licensing, DCO, and public-safety implications. Required checks are green and no actionable review threads remain.

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