[{"data":1,"prerenderedAt":76},["ShallowReactive",2],{"term-a\u002Fapproval-theater":3,"related-a\u002Fapproval-theater":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fa\u002Fapproval-theater.md","Approval Theater",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"Approval theater is when a pull request gets its required two approvals in under ninety seconds from reviewers who very clearly did not read a single line of the diff. The green checkmark is real, the actual review behind it is not, and everyone quietly knows it, but the process looks satisfied so the PR merges anyway.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Approval theater describes code review approvals granted as a formality to satisfy a branch protection rule or process requirement rather than reflecting genuine scrutiny of the change, often driven by review fatigue, unclear ownership, or social pressure to unblock a teammate quickly. It defeats the purpose of mandatory review gates and is typically addressed by reducing PR size, clarifying reviewer expectations, and treating review time as real, protected work rather than an interruption to it.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"That was approval theater, they LGTM'd it four minutes after it was opened.\" \u002F \"We started requiring a comment on every approval to cut down on approval theater.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"git","Approval theater is when a pull request gets its required two approvals in under ninety seconds from reviewers who very clearly did not read a single line...","intermediate","md","a",{},true,"\u002Fterms\u002Fa\u002Fapproval-theater",[49,50,51,52],"Code Review","LGTM","Review Fatigue","Rubber Stamping",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fa\u002Fapproval-theater","l9VVaT6X_Twl5cKArA9QpLJl4QBoeBeg5xxHVoOWY3w",[60,65,70,73],{"title":49,"path":61,"acronym":6,"category":62,"difficulty":63,"description":64},"\u002Fterms\u002Fc\u002Fcode-review","general","beginner","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":50,"path":66,"acronym":67,"category":68,"difficulty":63,"description":69},"\u002Fterms\u002Fl\u002Flgtm","Looks Good To Me","vibecoding","LGTM is the two-word code review approval that can mean anything from 'I carefully reviewed every line and this is perfect' to 'I glanced at the title and...",{"title":51,"path":71,"acronym":6,"category":68,"difficulty":63,"description":72},"\u002Fterms\u002Fr\u002Freview-fatigue","Review fatigue is PR fatigue's cousin — the mental exhaustion of reviewing code all day. After 8 reviews, you're not actually reading anything.",{"title":52,"path":74,"acronym":6,"category":62,"difficulty":63,"description":75},"\u002Fterms\u002Fr\u002Frubber-stamping","Approving a pull request without actually reading the code. Just clicking 'LGTM' and moving on. We've all done it. We've all been burned by it.",1792528061123]