| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Production-Ready GitHub Actions Automation Workflow with Claude Code
Transform your development workflow from planning to deployment in under 5 minutes. A comprehensive, production-ready blueprint that combines GitHub Actions with Claude Code for intelligent, automated workflows.
This repository provides a complete, copy-paste and production-ready blueprint for automating your entire GitHub workflow using GitHub Actions and Claude Code. From converting plans to issues, creating branches, running quality checks, to deploying to production—everything is automated, intelligent, and production-ready. This helps you to keep the context of your tasks preserved in an efficient way. You have installation script available to run through the installation routine and chose your suitable wokrflow.
Perfect for: Solo developers, small teams, and enterprises looking to streamline their development workflow with AI-powered automation.
Get up and running in 3 commands:
# 1. Clone this blueprint into your project
git clone https://github.com/alirezarezvani/claude-code-github-workflow.git .github-blueprint
cd .github-blueprint
# 2. Run the interactive setup wizard
./setup/wizard.sh
# 3. Verify everything is working
./setup/validate.shThat's it! Your repository now has:
Next Steps:
Reusable building blocks for DRY workflows:
Professional templates for consistency:
┌─────────────────────────────────────────────────────────────────┐
│ User Interface Layer │
│ (8 Slash Commands + Interactive Wizard) │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Automation Layer │
│ (4 Autonomous Agents + 5 Composite Actions) │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Workflow Layer │
│ (8 GitHub Actions Workflows + Projects v2 Sync) │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Foundation Layer │
│ (Git + GitHub + Claude Code v1 GA + Project Board) │
└─────────────────────────────────────────────────────────────────┘
graph TD
A[Claude Plan JSON] -->|claude-plan-to-issues.yml| B[GitHub Issues]
B -->|Labels: claude-code + status:ready| C[Auto-create Branch]
C -->|create-branch-on-issue.yml| D[Feature Branch]
D -->|Developer commits| E[Create PR to dev]
E -->|pr-into-dev.yml| F{Quality Checks}
F -->|Pass| G[Merge to dev]
F -->|Fail| E
G -->|pr-status-sync.yml| H[Issues: To Deploy]
H -->|Create PR: dev → main| I[Release Gates]
I -->|dev-to-main.yml| J{Release Checks}
J -->|Pass| K[Merge to main]
J -->|Fail| I
K -->|release-status-sync.yml| L[Close Issues ✅]
L -->|Optional| M[Create GitHub Release]
See Architecture Documentation for detailed system design.
Choose the strategy that fits your team:
feature/* → main fix/* → main hotfix/* → main
feature/* → dev → main fix/* → dev → main hotfix/* → dev → main
feature/* → dev → staging → main fix/* → dev → staging → main hotfix/* → staging → main (fast-track)
The blueprint supports all three strategies out of the box. Choose during setup.
The Release to Main workflow enforces the following rules:
feature/* → dev → main fix/* → dev → main test/* → dev → main
All feature, fix, and test branches must merge to dev first, then dev merges to main.
| Pattern | Purpose | Use Case |
|---|---|---|
| dev | Production releases | Standard release flow (only dev can merge to main) |
| release/* | Emergency hotfixes | Critical fixes bypassing dev (e.g., release/1.0.1-security) |
| dependabot/* | Dependency updates | Automated dependency update PRs |
Example:
# Standard flow (most common)
git checkout -b feature/new-feature
git push origin feature/new-feature
# Create PR: feature/new-feature → dev
# After merge, create PR: dev → main
# Emergency hotfix (rare)
git checkout -b release/1.0.1-security-patch
git push origin release/1.0.1-security-patch
# Create PR: release/1.0.1-security-patch → main (bypasses dev)Important: Attempting to merge feature/, fix/, or test/* branches directly to main will fail validation.
Built-in protections ensure safe, reliable automation:
→ 📖 Full Documentation Site - Modern docs with search & navigation → 📝 GitHub Wiki - Quick reference & community docs
Both sites auto-update from the docs/ folder on every commit to main.
After implementing this blueprint:
Minimum Requirements:
Optional:
Problem: "gh command not found" Solution: Install GitHub CLI: brew install gh (macOS) or see GitHub CLI docs
Problem: "PROJECT_URL not set" Solution: Run /blueprint-init to configure project board URL
Problem: "Workflow failed" Solution: Check recent runs: gh run list --limit 5 and view logs
Problem: "ANTHROPIC_API_KEY not set" Solution: Add your API key to repository secrets
See Troubleshooting Guide for more solutions.
Contributions are welcome! This is a blueprint designed to be customized and extended.
Be respectful, inclusive, and constructive. See CODE_OF_CONDUCT.md for details.
This project is licensed under the MIT License - see the LICENSE file for details.
This blueprint uses and extends:
Built with Claude Code v1 GA. All Claude Code features require an Anthropic API key.
Instead of spending weeks configuring workflows, get a production-ready system in 5 minutes.
This blueprint eliminates:
And provides:
Total: 70 deliverables (~33,000 lines of production-ready code)
⭐ If this blueprint helps you, please give it a star! ⭐
Made with ❤️ by Alireza Rezvani
Empowering developers with world-class automation 🚀
Assisted By Claude Code
| Back | FazBrowse Home | New Git URL |