Have you seen GitHub Agentic Workflows? It's pretty sick.
They are automated, intent-driven repository workflows that run in GitHub Actions, and they're authored in Markdown, and executed with coding agents.
In a bit more plain English: you describe the outcomes you want in plain Markdown, add this as an automated workflow to your repository, and it executes using a coding agent in GitHub Actions.
This brings the power of coding agents into the heart of repo automation. Agentic workflows run as standard GitHub Actions workflows, with added guardrails for sandboxing, permissions, control, and review.
In even plainer English: your repositories can automate themselves, securely.
Here's an example: imagine I have a repository that has a lot of contributors, and as a maintainer I want to keep an eye on what happens in the repo daily.
I can add the GitHub Agentic Workflows extension to the GitHub CLI, and then when I run it, I say, "Generate a workflow that creates a daily repo status report for a maintainer." From there, I can choose the agent to run the workflow, and it creates a GitHub Action in markdown in my repo. From then on, as a maintainer, I'll get a daily issue that has: Recent repository activity, progress tracking, project status, and actionable next steps.
This is just a simple example. Imagine making workflows that label your issues, or propose fixes to CI failures, or add testing to pull requests.
GitHub Agentic Workflows are available now in technical preview, and if you'd like to learn more, head over to the GitHub blog for documentation and details!