[{"data":1,"prerenderedAt":91},["ShallowReactive",2],{"term-c\u002Fcodeowners":3,"related-c\u002Fcodeowners":74},{"id":4,"title":5,"acronym":6,"body":7,"category":55,"description":56,"difficulty":57,"extension":58,"letter":59,"meta":60,"navigation":61,"path":62,"related":63,"seo":68,"sitemap":69,"stem":72,"subcategory":6,"__hash__":73},"terms\u002Fterms\u002Fc\u002Fcodeowners.md","CODEOWNERS",null,{"type":8,"value":9,"toc":48},"minimark",[10,15,19,23,26,30,41,45],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"CODEOWNERS is a file that turns who's-supposed-to-review-this from a Slack message into an automatic assignment. You map file paths to people or teams once, and from then on, every pull request that touches your billing folder automatically pings the billing team for review, without anyone having to remember or ask.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"CODEOWNERS is a plain text file, recognized by GitHub, GitLab, and Bitbucket, that maps glob path patterns to individual users or teams, automatically requesting their review on any pull request that modifies matching files and, when combined with branch protection rules, optionally requiring their explicit approval before merge. It's the standard mechanism for path based ownership in monorepos, letting many teams share one repository while each retains review authority over its own directories.",[11,27,29],{"id":28},"show-me-the-code","Show Me The Code",[31,32,38],"pre",{"className":33,"code":35,"language":36,"meta":37},[34],"language-text","# .github\u002FCODEOWNERS\n\u002Fapps\u002Fbilling\u002F     @team-billing\n\u002Fapps\u002Fcheckout\u002F    @team-checkout\n*.tf               @team-platform\npackage.json       @team-leads\n","text","",[39,40,35],"code",{"__ignoreMap":37},[11,42,44],{"id":43},"when-youll-hear-this","When You'll Hear This",[16,46,47],{},"\"CODEOWNERS auto-requested the billing team the second the PR touched that folder.\" \u002F \"Nobody owns that directory in CODEOWNERS, that's why reviews sit for days.\"",{"title":37,"searchDepth":49,"depth":49,"links":50},2,[51,52,53,54],{"id":13,"depth":49,"text":14},{"id":21,"depth":49,"text":22},{"id":28,"depth":49,"text":29},{"id":43,"depth":49,"text":44},"git","CODEOWNERS is a file that turns who's-supposed-to-review-this from a Slack message into an automatic assignment.","intermediate","md","c",{},true,"\u002Fterms\u002Fc\u002Fcodeowners",[64,65,66,67],"Pull Request","Branch Protection","Code Review","Monorepo",{"title":5,"description":56},{"changefreq":70,"priority":71},"weekly",0.7,"terms\u002Fc\u002Fcodeowners","kDoR_tiCooDIexw-T3bbkT4UWW-JvvlAUKP7NkewTxM",[75,80,84,87],{"title":65,"path":76,"acronym":6,"category":77,"difficulty":78,"description":79},"\u002Fterms\u002Fb\u002Fbranch-protection","cicd","beginner","Branch Protection puts a velvet rope around your main branch. No force pushes, no direct commits, mandatory reviews, required CI checks.",{"title":66,"path":81,"acronym":6,"category":82,"difficulty":78,"description":83},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":67,"path":85,"acronym":6,"category":82,"difficulty":57,"description":86},"\u002Fterms\u002Fm\u002Fmonorepo","A monorepo is when you put all your different projects — frontend, backend, shared libraries — in one giant single repository instead of separate repos.",{"title":64,"path":88,"acronym":89,"category":55,"difficulty":78,"description":90},"\u002Fterms\u002Fp\u002Fpull-request","PR","A pull request is like raising your hand in class and saying 'Hey, I made some changes — can someone check my work before we make it official?",1792528068719]