Repository navigation
.github/CODEOWNERS.md is not read as a code-owners file #72
Description
GitHub only reads a code-owners file named exactly CODEOWNERS ("create a new file called CODEOWNERS in the .github/, root, or docs/ directory of the repository", About code owners), so .github/CODEOWNERS.md is probably being ignored while the main ruleset asks for code-owner review.
Two ways to line them up: rename it to .github/CODEOWNERS, after which every PR to main needs an approval from one of the two listed owners (an author can't approve their own PR); or drop the code-owner rule and keep the one-approval rule. Which one did you intend?
Activity
qte77 commentedon Nov 14, 2026
A few small PRs are ready for review, one topic each: #70 (README: what runs without Docker or a key), #73 (licence gate for the publish set), #74 (test for the 0.3 critical cap on the judge path), #75 (stale lines in the runbook and criteria docs), #76 (README §3.1: which tasks run the lint), #77 (README §6 pointer to the risk register). Who should review them? It depends on the code-owners question above.
Related: the
deploy-hfjob inci.ymlneeds theHF_TOKENsecret; if that token stops working, the cleanup in #56 won't reach the dataset after merge.