[{"data":1,"prerenderedAt":89},["ShallowReactive",2],{"blog-securing-automation-approval-required-for-bot-created-pull-request-workflows":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"tags":11,"cover":16,"body":17,"_type":83,"_id":84,"_source":85,"_file":86,"_stem":87,"_extension":88},"/blog/securing-automation-approval-required-for-bot-created-pull-request-workflows","blog",false,"","Securing Automation: Approval Required for Bot-Created Pull Request Workflows","GitHub enhances security by requiring user approval for workflows triggered by bot-created pull requests.","2026-06-15",[12,13,14,15],"github","cicd","security","devops",true,{"type":18,"children":19,"toc":76},"root",[20,29,43,49,54,60,65,71],{"type":21,"tag":22,"props":23,"children":25},"element","h2",{"id":24},"new-security-measure-for-bot-created-pull-requests",[26],{"type":27,"value":28},"text","New Security Measure for Bot-Created Pull Requests",{"type":21,"tag":30,"props":31,"children":32},"p",{},[33,35,41],{"type":27,"value":34},"GitHub now requires explicit user approval for CI/CD workflows triggered by pull requests created by the github-actions",{"type":21,"tag":36,"props":37,"children":38},"span",{},[39],{"type":27,"value":40},"bot",{"type":27,"value":42},". This new policy serves as an important security measure to prevent automated code from executing without oversight.",{"type":21,"tag":22,"props":44,"children":46},{"id":45},"why-this-matters",[47],{"type":27,"value":48},"Why This Matters",{"type":21,"tag":30,"props":50,"children":51},{},[52],{"type":27,"value":53},"Automation is key in modern development pipelines but also introduces security risks if unchecked code executes automatically. By requiring approval, GitHub ensures that generated code from bots doesn't run workflows without human validation.",{"type":21,"tag":22,"props":55,"children":57},{"id":56},"balancing-automation-and-security",[58],{"type":27,"value":59},"Balancing Automation and Security",{"type":21,"tag":30,"props":61,"children":62},{},[63],{"type":27,"value":64},"This update reflects a growing awareness of security concerns in automation workflows. It empowers users to benefit from automated pull requests while maintaining control, reducing risk in collaborative development environments.",{"type":21,"tag":22,"props":66,"children":68},{"id":67},"conclusion",[69],{"type":27,"value":70},"Conclusion",{"type":21,"tag":30,"props":72,"children":73},{},[74],{"type":27,"value":75},"This approval step enhances the integrity of CI/CD processes by adding a checkpoint for bot-generated code execution, aligning workflow automation with best security practices.",{"title":7,"searchDepth":77,"depth":77,"links":78},2,[79,80,81,82],{"id":24,"depth":77,"text":28},{"id":45,"depth":77,"text":48},{"id":56,"depth":77,"text":59},{"id":67,"depth":77,"text":70},"markdown","content:blog:securing-automation-approval-required-for-bot-created-pull-request-workflows.md","content","blog/securing-automation-approval-required-for-bot-created-pull-request-workflows.md","blog/securing-automation-approval-required-for-bot-created-pull-request-workflows","md",1781507934981]