ci-workflows

Pin GitHub Actions and Gitea Actions workflow versions with YAML compatibility rules.

1|Updated Mar 18, 2024
One-click install
npx skills add https://github.com/erfianugrah/dotfiles --skill ci-workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-workflows
Source: https://github.com/erfianugrah/dotfiles/tree/main/.pi/agent/skills/ci-workflows
Command: npx skills add https://github.com/erfianugrah/dotfiles --skill ci-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken CI pipelines by ensuring GitHub Actions and Gitea Actions workflows are pinned to verified-current action versions and written with Gitea-compatible YAML patterns.

Core Features & Use Cases

  • Verified-current action pinning: Converts “use whatever the latest is” into safe major-tag pins (and notes when SHA pinning is warranted).
  • GitHub vs Gitea compatibility coverage: Documents and accounts for fields and behaviors that Gitea silently ignores, runner label/image differences, and action download source differences.
  • Practical workflow guidance: Provides templates and patterns for Node/Python/Go/Java/Bun/Deno, Docker build+push, Pages deployment, and GitHub Releases, plus a re-verification protocol to avoid stale versions.

Quick Start

Use ci-workflows to review a workflow YAML and rewrite it so each uses: action is pinned to the verified major tag for both GitHub Actions and Gitea Actions where applicable.

Frequently Asked Questions about ci-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pin GitHub Actions to specific versions in workflow YAML?

Pin GitHub Actions by replacing floating latest tags with verified major tags in your workflow YAML `uses:` declarations, applying SHA pinning when strict reproducibility is warranted for critical pipelines.

Does Gitea Actions support the same workflow YAML fields as GitHub Actions?

Gitea Actions silently ignores specific GitHub Actions workflow YAML fields and requires distinct runner label and image mappings, meaning migrated workflows need compatibility auditing to run reliably.

How do I migrate CI workflows from GitHub to Gitea?

Migrate CI workflows by moving files to `.gitea/workflows`, mapping runner labels and images, accounting for silently ignored fields, and applying verified major-tag action pinning to ensure cross-platform reliability.

What is the best way to prevent broken CI pipelines from outdated action versions?

Prevent broken CI pipelines by applying verified major-tag pinning alongside a webfetch-based re-verification protocol to check for current action versions before updating workflow YAML dependencies.

Can I use this to audit Docker build and push workflows for Gitea compatibility?

Yes, you can audit Docker build and push workflows by validating YAML patterns against Gitea compatibility rules, mapping runner labels, and verifying action pins for both GitHub and Gitea Actions platforms.

Why does my Gitea Actions workflow ignore certain deployment configuration fields?

Gitea Actions silently ignores specific GitHub Actions configuration fields, causing pages deployment and release publishing patterns to fail unless rewritten with Gitea-compatible YAML rules.