Add CODEOWNERS with conditional review ownership #74
Labels
No labels
automation
automerge
ci
infra
migrated/beads
priority/P2
refactoring
repo-maintenance
status/in-progress
testing
type/epic
type/task
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
Personal/cluster#74
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add or adapt the CODEOWNERS file, checking existing branches and how CODEOWNERS is configured in the user's other repositories. Configure AI as an owner for all changes. Add clank-bot only for functional changes that are not Renovate dependency updates, so Renovate-only changes do not trigger a clank-bot review. An existing remote branch, origin/migrate/codeowners, contains an older CODEOWNERS change that should be reviewed and adapted rather than duplicated blindly.
Acceptance criteria
A CODEOWNERS file follows the established pattern from the user's other repositories where appropriate; AI is requested on every change; clank-bot is requested only for functional changes not covered by Renovate updates; Renovate-only dependency updates do not request clank-bot; any existing branch work is identified and coordinated rather than duplicated.
Notes
Found an existing historical commit (
5ed4bf2, 'Migration: codeowners') in repository history; inspect its original branch/contents when implementing. Current local branch list has no obvious CODEOWNERS branch.Confirmed origin/migrate/codeowners contains commit
5ed4bf2('Migration: codeowners') adding CODEOWNERS with '* @martin @clank-bot'. This blanket clank-bot rule does not meet the conditional review requirement; reuse/adapt the branch as appropriate.Beads migration
Original ID:
cluster-jtd· Status:open· Priority: P2 · Type: taskOriginal timestamps and metadata are preserved below; Forgejo's native timestamps reflect the migration.
Original Beads record