- You are...
- You'll get...
- A developer new to agentic workflows
- A clear, end-to-end path from zero to a working automation
- A GitHub Actions user
- A practical mental model for when agentic workflows are a better fit than classic YAML and scripts
- A platform or DevOps engineer
- A reusable pattern for AI-assisted repository triage with auditable runs in GitHub
Specs
- You are...You'll get...
- A developer new to agentic workflowsA clear, end-to-end path from zero to a working automation
- A GitHub Actions userA practical mental model for when agentic workflows are a better fit than classic YAML and scripts
- A platform or DevOps engineerA reusable pattern for AI-assisted repository triage with auditable runs in GitHub
- An evaluator, mentor, or workshop hostA hands-on artifact that makes agentic workflow concepts easy to demonstrate and assess
README
GitHub Agentic Workflows Factory Tour
[!IMPORTANT]
GitHub Agentic Workflows and thegh-awCLI are in public preview. You may notice product changes, rough edges, or minor differences from the screenshots and examples in this workshop.
What you will learn to build
Build a real AI-powered GitHub workflow from scratch and leave with a safe production-style agentic automation you can adapt to your own repositories.
<picture>
<source media="(prefers-color-scheme: dark)" srcset="workshop/images/00-daily-repo-status-output-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="workshop/images/00-daily-repo-status-output-light.svg">
<img src="workshop/images/00-daily-repo-status-output-light.svg" alt="Sample daily repository status report generated by the finished workflow" width="600">
</picture>
Why this workshop
Most workflow tutorials stop at toy examples. This workshop takes you all the way to a useful end result: an agentic workflow that runs in GitHub Actions, inspects a repository, and publishes a daily status report automatically.
By the time you finish, you will know how to:
- define an agentic workflow in Markdown
- use the
gh-awCLI to validate, run, and iterate on workflows - connect triggers, prompts, and GitHub context into one practical automation
- adapt the pattern for scheduled reporting, documentation upkeep, PR review, and more
What you'll build
You'll build a scheduled, AI-powered repository status report that runs in GitHub Actions and posts a useful summary without custom shell-script orchestration.
<picture>
<source media="(prefers-color-scheme: dark)" srcset="workshop/images/00-workflow-run-complete-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="workshop/images/00-workflow-run-complete-light.svg">
<img src="workshop/images/00-workflow-run-complete-light.svg" alt="Preview of a completed workflow run in the GitHub Actions UI" width="600">
</picture>
Who this is for
| You are... | You'll get... |
|---|---|
| A developer new to agentic workflows | A clear, end-to-end path from zero to a working automation |
| A GitHub Actions user | A practical mental model for when agentic workflows are a better fit than classic YAML and scripts |
| A platform or DevOps engineer | A reusable pattern for AI-assisted repository triage with auditable runs in GitHub |
| An evaluator, mentor, or workshop host | A hands-on artifact that makes agentic workflow concepts easy to demonstrate and assess |
What makes this different from a classic Actions tutorial
Instead of spending most of your time wiring together scripts, conditionals, and API calls, you define the workflow in a Markdown brief and let the agent reason over the repository at runtime.
That means you focus on:
- the task you want completed
- the repository context the agent should use
- the trigger that should run the workflow
- the output that should be published back to GitHub
Ready to begin?
:arrow_right: Start with workshop/00-welcome.md
[!NOTE]
Microsoft and GitHub facilitators: Request a demo environment at aka.ms/golden-ticket.
:copyright: GitHub • Code of Conduct • MIT License