agentleFS
komlukkomluk/scaffolding/skills/github-actions-template/SKILL.md

github-actions-template

Skill16 starsChanged 4 days agoMITView on GitHub

GitHub Actions CI pipeline templates and workflow YAML patterns. TRIGGER when: creating or editing a CI workflow, adding a CI job, or wiring build/test/deploy steps. SKIP: container build internals (use docker-templates); local git workflow (use git-operations).

  • Reads credentials

The file

Files
SKILL.md

Standard CI Pipeline

name: CI

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

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

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run lint

  type-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run type-check

  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run test

  build:
    runs-on: ubuntu-latest
    needs: [lint, type-check, test]
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run build
      - uses: actions/upload-artifact@v4
        with:
          name: build
          path: dist/

Pipeline Stages

StagePurposeFailure Action
LintCode style enforcementBlock merge
Type-checkTypeScript validationBlock merge
TestUnit/integration testsBlock merge
BuildProduction buildBlock merge
Deploy (staging)Preview deploymentWarn only
Deploy (prod)Production releaseManual approval

Environment Management

EnvironmentBranchAuto-deployApproval
Developmentfeature/*NoNone
StagingdevelopYesNone
ProductionmainYesRequired

Secrets Management

# GitHub Secrets (never in code)
env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}
  API_KEY: ${{ secrets.API_KEY }}

# Environment files (local only)
# .env.local - Never committed
# .env.example - Template only, no real values

Deployment Strategies

StrategyUse WhenRollback
Blue-GreenZero downtime criticalSwitch back to previous env
CanaryRisk mitigation, gradual rolloutRoute 100% to old version
RollingResource constrained, stateless appsSlower, redeploy previous

Rollback Triggers

Automated rollback when:

  • Health check failures after deploy
  • Error rate spike > 5%
  • Response time degradation
  • Memory/CPU threshold breach

Requirements: Keep N-1 version deployable, backward-compatible DB migrations, feature flags for risky changes.

Quality Gates

StageThreshold
Unit tests100% pass, > 70% coverage
Lint/FormatZero errors
Security scanNo critical vulnerabilities
BuildCompiles without errors

Pipeline Optimization Targets

StageTarget Time
Build< 5 min
Unit tests< 5 min
Integration tests< 10 min
Full pipeline< 30 min

Parallelize independent stages. Cache dependencies. Use incremental builds.

Bundled References

Usable workflow templates in references/ based on actual project CI:

FileDescription
references/ci-template.ymlFull CI pipeline with path filtering, backend (Python) + frontend (TS), SonarQube

Template uses self-hosted runner, dorny/paths-filter for conditional jobs, and artifact uploads for coverage. Adapt paths and language versions for new projects.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.