12 Automation Features

🤖 Automation Features

Quick intro: Comprehensive automation suite that streamlines development workflows, enhances code quality, and provides intelligent repository management with minimal manual intervention.

Note: This page focuses on automation features and benefits. For technical implementation details, see Workflow Details.

Overview

Zopio leverages 13 intelligent workflows to create a comprehensive automation ecosystem that:

🎯 Streamlines development with intelligent PR management
🛡️ Enhances security through automated scanning and vulnerability detection
🧹 Maintains repository health with automated housekeeping
👥 Improves contributor experience with welcoming and guidance systems
⚡ Optimizes performance with smart concurrency controls and triggers

🏗️ Workflow Architecture

View all 13 workflows and their purposes

Workflow	Purpose	Triggers
pr-validation.yml	Unified PR checks (naming, size, format)	All PRs
label.yml	Smart auto-labeling	PR open/edit
pr-assignment.yml	Intelligent assignment	PR open
ci.yml	Fast quality checks	Push & PR
build.yml	Comprehensive validation	PR to main
security.yml	Unified security suite	Push, PR, Daily
welcome.yml	First-timer greetings	Issues & PRs
stale.yml	Cleanup management	Daily schedule
lock-threads.yml	Archive old threads	Daily schedule
changelog.yml	Auto-generate notes	Push to main
release.yml	Publish releases	Push to main
docs.yml	Documentation checks	Docs changes
setup-node.yml	Reusable Node setup	Called by others

📊 Automation Impact Statistics

Metric	Before Automation	After Automation	Improvement
PR Review Time	30-45 min	15-20 min	50-60% faster
Security Issue Detection	Manual, weekly	Automated, daily	7x more frequent
Stale Issue Management	Manual cleanup	Automated lifecycle	100% coverage
Dependency Updates	Manual, monthly	Automated, weekly	4x more frequent
GitHub Actions Usage	High resource usage	Optimized with concurrency	40-50% reduction

Quick Start

🚀 Get started with automation in 3 steps

1️⃣ Understand Automatic Triggers

# These actions happen automatically when you:
Create PR     → Labeling, assignment, validation, security scan
Push to main  → Release automation, security scan, changelog
Daily at 2AM  → Stale management, security scan, dependency check

2️⃣ Check Automation Status

# View current automation status
gh workflow list                    # See all workflows
gh run list --limit 10              # Recent workflow runs
gh pr list --label="automated"      # Auto-managed PRs

3️⃣ Leverage Smart Features

✅ Use conventional commit messages for automatic labeling
✅ Follow branch naming conventions for automatic assignment
✅ Let automation handle routine tasks while you focus on coding

🎆 PR Automation Suite

🤖 Intelligent systems that transform PR management from manual to magical

💡 What This Means For You

⏱️ Time Savings Calculator

Manual Task	Time Before	Time After	Your Benefit
Labeling PRs	2-3 min	0 sec	✨ Auto-labeled on creation
Assigning reviewers	1-2 min	0 sec	✨ Smart assignment by code area
Validating format	5-10 min	Instant	✨ Real-time feedback
Finding reviewers	3-5 min	0 sec	✨ CODEOWNERS integration

Total saved per PR: ~15-20 minutes 🚀

🏷️ Intelligent Auto-Labeling System

Our sophisticated multi-source labeling system automatically categorizes PRs using:

flowchart TD
    PR[Pull Request] --> LABEL{Label Sources}
    LABEL --> PATH[Path-based<br/>labeler.yml]
    LABEL --> TITLE[Title parsing<br/>Conventional commits]
    LABEL --> PRIORITY[Priority keywords<br/>critical, urgent]
    LABEL --> BREAKING[Breaking changes<br/>! detection]
    LABEL --> COMMUNITY[Contributor status<br/>Org membership]
    
    PATH --> APPLY[Apply Labels]
    TITLE --> APPLY
    PRIORITY --> APPLY
    BREAKING --> APPLY
    COMMUNITY --> APPLY

🏷️ Label Categories:

Category	Trigger	Examples
🏢 Component	File paths	`frontend`, `backend`, `database`, `documentation`
🎨 Type	PR title	`type: feature`, `type: fix`, `type: docs`, `type: chore`
⚡ Priority	Keywords	`priority: critical`, `priority: high`
⚠️ Special	Content analysis	`breaking change`, `community contribution`

🎯 Smart PR Assignment

Intelligent assignment system based on code ownership and team expertise:

flowchart LR
    PR[PR Created] --> CHECK{Check Files}
    CHECK --> AUTH[Auth packages?]
    CHECK --> DB[Database?]
    CHECK --> CORE[Core packages?]
    CHECK --> SEC[Security files?]
    
    AUTH --> TEAM[Assign Core Team]
    DB --> TEAM
    CORE --> TEAM
    SEC --> TEAM
    
    PR --> AUTHOR[Assign to Author]

📝 Assignment Rules:

✅ PR author always assigned for tracking
✅ Team reviewers based on changed files
✅ Respects manual assignments
✅ Skips draft PRs for reviewers

✅ PR Validation Framework

Comprehensive validation suite ensures PR quality before review:

flowchart TB
    SUBMIT[PR Submitted] --> VAL{Validation Checks}
    
    VAL --> BRANCH[Branch Naming]
    VAL --> TITLE[Title Format]
    VAL --> SIZE[Size Limits]
    VAL --> BREAK[Breaking Changes]
    
    BRANCH --> RESULT{Pass?}
    TITLE --> RESULT
    SIZE --> RESULT
    BREAK --> RESULT
    
    RESULT -->|Yes| READY[Ready for Review]
    RESULT -->|No| COMMENT[Add Comment<br/>with Guidance]

📋 Validation Requirements:

Check	Requirements	Failure Action
Branch Naming	`feat/`, `fix/`, etc.	Comment with patterns
PR Title	Semantic format	Error with examples
Size Limits	<5000 lines, <100 files	Block with explanation
Breaking Changes	Documentation required	Request description

📝 Pro Tip: All validation runs in a single workflow for faster feedback!

⬆ Back to Top

🧹 Repository Maintenance

🤖 Self-healing repository management that keeps your workspace clean and organized

🗓️ Stale Item Management

Automated lifecycle management for issues and PRs prevents backlog bloat:

stateDiagram-v2
    [*] --> Active: New Issue/PR
    Active --> Inactive: No activity
    Inactive --> Stale: 60d (issues) / 30d (PRs)
    Stale --> Warning: Bot comments
    Warning --> Closed: 14d (issues) / 7d (PRs)
    Warning --> Active: User responds
    Closed --> Locked: 90d (issues) / 60d (PRs)

🛡️ Protected Items (Never marked stale):

🔒 Security items
📍 Pinned items
🌟 Good first issues
⚡ High priority items
💬 Blocked discussions

🔒 Thread Locking Policy

Prevents necroposting while preserving historical context:

⏰ Lock Timing:

📝 Issues: 90 days post-closure
🔀 PRs: 60 days post-closure

💬 Lock Messages:

Type	Message
Issues	"This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs."
PRs	"This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or a new PR for further contributions."

⬆ Back to Top

👥 Community Engagement

🎉 Creating a welcoming environment that turns first-time visitors into long-term contributors

👋 First-Time Contributor Welcome

Personalized welcome system that guides new contributors:

flowchart LR
    NEW[New Contributor] --> TYPE{Contribution Type}
    TYPE --> ISSUE[First Issue]
    TYPE --> PR[First PR]
    
    ISSUE --> WELCOME1[Issue Welcome<br/>+ Resources]
    PR --> WELCOME2[PR Welcome<br/>+ Guidelines]

🎁 Welcome Features:

📬 Personal @mention and greeting
📚 Contributing guidelines link
🔗 Resource recommendations for getting started
💪 Encouragement message with next steps
🎯 Tailored content for issues vs PRs

📚 See also: Welcome Messages for technical implementation

🌍 Community Contribution Detection

Automatic identification of external contributors:

// Simplified detection logic
try {
  await checkOrgMembership(author);
  // Member - no label
} catch (error) {
  if (error.status === 404) {
    // Non-member - add community label
    addLabel('community contribution');
  }
}

🎨 Result: External contributions automatically get the community contribution label for recognition!

⬆ Back to Top

🚀 Release Automation

📦 Zero-touch release pipeline from commit to production deployment

📝 Changelog Generation

Automated changelog from conventional commits:

flowchart LR
    COMMITS[Conventional<br/>Commits] --> ANALYZE[Analyze Types]
    ANALYZE --> VERSION[Determine<br/>Version Bump]
    VERSION --> CHANGELOG[Generate<br/>Changelog]
    CHANGELOG --> TAG[Create Tag]
    TAG --> RELEASE[GitHub Release]

🔢 Version Bumping Rules:

fix: → Patch (1.0.x) - Bug fixes
feat: → Minor (1.x.0) - New features
feat!: or BREAKING CHANGE → Major (x.0.0) - Breaking changes

📦 Release Artifacts:

GitHub Release with changelog notes
NPM Package auto-published
Build Assets attached to release
Team Notifications via GitHub & email

⚙️ Release Pipeline

Fully automated release process with zero manual intervention:

Step	Action	Automation
1️⃣	Trigger	Push to main (without `ci skip`)
2️⃣	Version	Auto-determined from commits
3️⃣	Changelog	Generated and committed
4️⃣	Tag	Created with version
5️⃣	Release	GitHub release with notes
6️⃣	Publish	NPM package deployment

💫 Magic: From code push to published package in under 5 minutes!

⬆ Back to Top

🛡️ Security Automation

🔍 Multi-layered security automation that never sleeps

🎯 Quick Security Overview

Continuous security scanning with multiple detection layers:

flowchart TB
    subgraph "Scheduled Scans"
        DAILY[Daily 2 AM UTC] --> SCAN
    end
    
    subgraph "Event-Driven Scans"
        PUSH[Code Push] --> SCAN
        PR[Pull Request] --> SCAN
    end
    
    SCAN{Security Suite} --> RESULTS[Security Tab]
    SCAN --> ALERTS[GitHub Alerts]
    SCAN --> BLOCK[Block if Critical]

📋 Security Automation Features:

🕵️‍♂️ CodeQL Analysis - Code vulnerability scanning
📦 Dependency Scanning - Known CVE detection
🔑 Secret Detection - Exposed credentials prevention
🔄 Automated Updates - Security patch management

📚 For complete security details: See 🛡️ Security Framework

🔐 Security Automation Highlights:

Container scanning for Docker images
SARIF reporting to GitHub Security tab
Email alerts for high-severity findings
Auto-blocking for critical vulnerabilities

⬆ Back to Top

⚡ Efficiency Features

🚀 Performance optimizations that deliver 40-50% reduction in GitHub Actions usage

🎯 Concurrency Management

Smart concurrency control prevents resource waste and speeds up feedback:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

🎯 How Concurrency Works:

Group Creation: Each workflow-branch combo gets a unique group
New Push Detection: When you push new commits
Auto-Cancellation: Outdated runs stop immediately
Latest Runs: Only the newest changes are validated
Resource Savings: No wasted compute on stale code

🎨 Benefits:

✅ Cancels outdated runs when new commits pushed
✅ Preserves latest changes for immediate feedback
✅ Reduces queue time by eliminating backlog
✅ Saves compute resources and costs

📂 Path-based Triggers

Intelligent triggering based on file changes saves resources:

paths-ignore:
  - '**/*.md'
  - 'docs/**'
  - 'LICENSE'

📂 Smart Path Detection Examples:

Component-based triggers

# From labeler.yml - Auto-labels based on paths
'package: auth':
  - packages/auth/**/*
  - packages/auth-*/**/*

'frontend':
  - apps/web/**/*
  - '**/*.tsx'
  - '**/*.css'

'backend':
  - apps/api/**/*
  - packages/database/**/*

🎨 Advantages:

✅ Skip unnecessary builds for docs-only changes
✅ Faster feedback on code changes
✅ Resource optimization for meaningful work
✅ Focus on code changes that matter

⬆ Back to Top

🚀 Advanced Automation Features

🔧 Enterprise-grade features that set Zopio apart

🌿 Multi-Branch Operations

🔀 Hotfix Dual-Merge:

When creating hotfixes, automation ensures:

✅ Merge to main for immediate deployment
✅ Automatic backport to develop
✅ Conflict detection and alerts
✅ Maintains version consistency

flowchart LR
    HF[Hotfix Branch] --> M1[Merge to Main]
    HF --> M2[Merge to Develop]
    M1 --> D[Deploy]
    M2 --> S[Sync]

🧪 Staging E2E Automation

🎭 Automated E2E Testing:

When code reaches staging:

Deployment trigger activates E2E suite
Playwright tests run against staging URL
Visual regression checks for UI changes
Performance metrics collected
Auto-rollback on critical failures

📊 Conditional Workflow Execution

⚡ Smart Workflow Triggers:

# Example: Only run expensive checks when needed
if: |
  contains(github.event.pull_request.labels.*.name, 'needs-benchmark') ||
  contains(github.event.head_commit.message, '[benchmark]')

Common Conditions:

🏷️ Label-based triggers
📝 Commit message flags
👤 Author permissions
📁 File change patterns

⬆ Back to Top

📋 Automation Benefits Summary

📈 Quantified impact of our automation suite on development workflow

📊 Time & Quality Impact

Feature	⏱️ Time Saved	🎨 Quality Impact	💰 Value
Auto-labeling	2-3 min/PR	Consistent categorization	High
PR validation	5-10 min/PR	Enforced standards	Critical
Auto-assignment	1-2 min/PR	Faster reviews	Medium
Stale management	30 min/week	Clean backlog	High
Security scanning	2 hours/week	Early detection	Critical
Release automation	30 min/release	Consistent process	High

📊 Total Weekly Savings: ~6-8 hours of manual work per developer

🎯 Quick Reference Card

🤖 What Happens Automatically

When You...	Automation Response
📝 Create PR	→ Labels, assignment, validation, security scan
🚀 Push to main	→ Release, changelog, security scan
🌅 Daily at 2AM	→ Stale cleanup, security scan, dependency check
👋 First contribution	→ Welcome message, guidance, community label
⚠️ Breaking change	→ Documentation requirement, special handling

🛠️ Troubleshooting

🔧 Common Issues & Solutions

❌ Workflow Not Triggering

Problem: Expected automation didn't run Solution:

Check if paths-ignore filters excluded your changes
Verify branch naming follows conventions
Ensure required secrets are configured

⚠️ Labels Not Applied

Problem: PR not getting automatic labels Solution:

Use conventional commit format in PR title
Check if files match labeler.yml patterns
Verify labeler workflow has necessary permissions

🔒 Security Scan Failures

Problem: Security workflow blocking PRs Solution:

Review security scan results in Security tab
Fix identified vulnerabilities before merging
Add exceptions for false positives (with approval)

💬 Stale Bot Issues

Problem: Important issues marked as stale Solution:

Add pinned label to prevent stale marking
Use security label for security-related items
Comment on issue to reset stale timer

📍 Next Steps

🚀 Take Action

📚 Learn More

Read Workflow Details for technical implementation
View Workflow Architecture for system design
Check Pipeline Overview for CI/CD details
Review Best Practices for optimization tips

🔧 Customize Automation

Modify .github/labeler.yml for custom labels
Adjust .github/workflows/ files for your needs
Configure Dependabot in .github/dependabot.yml

📊 Monitor Performance

Review GitHub Actions usage in Settings
Track automation effectiveness with metrics
Optimize workflows based on usage patterns

📚 Related Pages

Page	Purpose	Why Read
🔧 Workflow Details	Technical implementation	Configuration deep-dive
🏗️ Workflow Architecture	System design	How workflows interact
🚀 Pipeline Overview	CI/CD pipeline	Build & deploy process
📊 Triggers Matrix	Trigger reference	When workflows run
🛡️ Security Framework	Security details	Complete security guide
🎆 Best Practices	Optimization tips	Performance tuning

⬆ Back to Top

Uh oh!

12 Automation Features

🤖 Automation Features

🗺️ Quick Navigation

Overview

🏗️ Workflow Architecture

Quick Start

1️⃣ Understand Automatic Triggers

2️⃣ Check Automation Status

3️⃣ Leverage Smart Features

🎆 PR Automation Suite

💡 What This Means For You

🏷️ Label Categories:

📝 Assignment Rules:

📋 Validation Requirements:

🧹 Repository Maintenance

🛡️ Protected Items (Never marked stale):

⏰ Lock Timing:

💬 Lock Messages:

👥 Community Engagement

🎁 Welcome Features:

🚀 Release Automation

🔢 Version Bumping Rules:

📦 Release Artifacts:

🛡️ Security Automation

📋 Security Automation Features:

🔐 Security Automation Highlights:

⚡ Efficiency Features

🎯 How Concurrency Works:

🎨 Benefits:

📂 Smart Path Detection Examples:

🎨 Advantages:

🚀 Advanced Automation Features

🔀 Hotfix Dual-Merge:

🎭 Automated E2E Testing:

⚡ Smart Workflow Triggers:

📋 Automation Benefits Summary

📊 Total Weekly Savings: ~6-8 hours of manual work per developer

🤖 What Happens Automatically

🛠️ Troubleshooting

❌ Workflow Not Triggering

⚠️ Labels Not Applied

🔒 Security Scan Failures

💬 Stale Bot Issues

📍 Next Steps

📚 Learn More

🔧 Customize Automation

📊 Monitor Performance

📚 Related Pages

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Clone this wiki locally