GitHub Agentic Workflows
Agentic workflow tool in Developer tools
People like the idea of markdown-defined agents handling event-driven chores like triage, docs sync and CI fixes. Critics warn about security, especially running on public repos, and the overhead of AI in workflows.
People like the idea of markdown-defined agents handling event-driven chores like triage, docs sync and CI fixes. Critics warn about security, especially running on public repos, and the overhead of AI in workflows.
42 people gave an opinion
- recommend it
- 17
- criticize it
- 25
- approval share
- 40%
Recommended in 6 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 17 people recommend itNeeds 10 or more, met.
- 0.6 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 6 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Compelling markdown-defined agent concept
“Similar idea (rooted on "agents as markdown") but on the outer loop is taking shape at GitHub with GitHub Agentic Workflows.”
Comment from 15 Mar 2026 in “Show HN: GitAgent – An open standard that turns any Git repo into an AI agent” “mostly because I believe it is a great idea, and I am experimenting on it myself”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” “We find that there's something very compelling about the shape of this”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” Delegates routine chores to agents
“it looks solid for the event-driven automation shape (triage, docs sync, CI fix)”
Comment from 11 Apr 2026 on Hacker News “The value is "delegate chores that cannot be handled by a heuristic".”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” Saves time on reviews and research
“create a simple but effective usage for my day 2 day reviews”
Comment from 20 Feb 2026 in “Mixing the new GitHub agent workflow and Jira MCP to accelerate PR review” “this feature alone has saved me days of work/research”
Comment from 3 Dec 2025 in “Zig quits GitHub, says Microsoft's AI obsession has ruined the service” Solid security controls out of the box
“This is a solid step forward on execution safety for agentic workflows.”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” “come with many additional security controls out of the box”
Comment from 14 Apr 2026 in “Claude Code Routines”
What people warn about
Each mark is one comment
Security model and public repo risks
“they still have some work to do, either on the security model”
Comment from 8 Jul 2026 in “GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos” “It seems like the proper fix is for GitHub not to allow their agentic workflow to execute in a public repo context”
Comment from 8 Jul 2026 in “GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos” “I'm certainly not going to trust them with access to information and then allow anyone to send them prompts.”
Comment from 8 Jul 2026 in “GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos” - Comment from 9 Feb 2026 in “GitHub Agentic Workflows”
- Comment from 9 Jul 2026 in “GitLost: We Tricked GitHub's AI Agent into Leaking Private Repos”
Hallucinated or incorrect fixes
“The copilot agent then implemented that by adding a replace statement, which is not how you are supposed to do this.”
Comment from 9 Feb 2026 in “GitHub Agentic Workflows” “hallucinations that then churn through I don't know how many tokens trying to "fix it"”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” “I feel like this solution hallucinated the concept of Workflow Lock File”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” Billing errors despite paying
“I paid or tried to for the extra billing, I followed all the instructions and still got the same error.”
Comment from 9 Feb 2026 in “GitHub Agentic Workflows” “we pay them for the actions and everything and still ran into this issue”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” “even when I tried to pay, it was still failing under the same error”
Comment from 9 Feb 2026 in “GitHub Agentic Workflows” Overhead and unnecessary AI use
“always running your action from a Markdown file seems extremely wasteful in terms of resources”
Comment from 8 Dec 2025 in “GitHub Actions has a package manager, and it might be the worst” “That is literally just creating overhead for me and it sounds like an excuse to shoehorn AI in to a workflow more than anything else.”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows” “I find this confusing: I can see the value in having an LLM assist you in developing a CI/CD workflow”
Comment from 8 Feb 2026 in “GitHub Agentic Workflows”
What people said
40 of the 46 comments that mention it, newest first. Each links to the original comment.
“this feature shouldn't have been delivered where this is an allowed state”
“This fails security protocols established 25+ years ago.”
“they still have some work to do, either on the security model”
“It seems like the proper fix is for GitHub not to allow their agentic workflow to execute in a public repo context”
“It's insane that no one tried this internally during development”
“I'm certainly not going to trust them with access to information and then allow anyone to send them prompts.”
“require a bit more handholding and testing to work”
“seems like this would solve it”
“come with many additional security controls out of the box”
“it looks solid for the event-driven automation shape (triage, docs sync, CI fix)”
“GitHub agentic workflows gets you 95% of the way there already.”
“Similar idea (rooted on "agents as markdown") but on the outer loop is taking shape at GitHub with GitHub Agentic Workflows.”
“Fixes are deployed to our staging env in 10 minutes.”
“create a simple but effective usage for my day 2 day reviews”
“it is a good indicator to stay far far away”
“presumably slophub's now dogfooding GitHub Agentic Workflows?”
“GH misrepresenting its software and people being surprised by the many minor bugs”
“The copilot agent then implemented that by adding a replace statement, which is not how you are supposed to do this.”
“makes all the GitHub agent stuff feel pointless to me”
“even when I tried to pay, it was still failing under the same error”
“I paid or tried to for the extra billing, I followed all the instructions and still got the same error.”
“GitHub Actions is the last organization I would trust to recognize a security-first design principle.”
“Why are they pushing this nonsense on developers when the real money is in surveillance and web indexing?”
“Separating the LLM invocation from the apply step is a great idea.”
“That is literally just creating overhead for me and it sounds like an excuse to shoehorn AI in to a workflow more than anything else.”
“The value is "delegate chores that cannot be handled by a heuristic".”
“We find that there's something very compelling about the shape of this”
“They need to fix everything before pasting more shit on top.”
“mostly because I believe it is a great idea, and I am experimenting on it myself”
“we pay them for the actions and everything and still ran into this issue”
“This is a solid step forward on execution safety for agentic workflows.”
“hallucinations that then churn through I don't know how many tokens trying to "fix it"”
“That's something that really should have an extra confirmation.”
“I find this confusing: I can see the value in having an LLM assist you in developing a CI/CD workflow”
“I feel like this solution hallucinated the concept of Workflow Lock File”
“Shit slop which will be irrelevant in less than a year time”
“Not confirmed that it's by Github, phishy domain.”
“always running your action from a Markdown file seems extremely wasteful in terms of resources”
“this feature alone has saved me days of work/research”
“this time Github AI actually have a useful answer”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.