Menu

How I centralized GitHub Actions across my repositories
📰

How I centralized GitHub Actions across my repositories

DEV Community: cicd·Miguel Valdes·10 days ago
#8NAxN5PZ
#devtocicd#devto#dev#workflow#repository
Reading 0:00
15s threshold

I maintain "enough" repositories that copying the same GitHub Actions workflows into each one became a real PITA. Most are created and managed as code, with their configuration baked in from the start. That includes container secrets, registry settings, service API keys, tests, and linting. Every improvement meant changing the same YAML again and again.

This reminded me of a pattern from my enterprise days. Teams kept shared CI/CD workflows in a handful of repositories and consumed them as internal services. I am my own tiny cloud and company, so I borrowed the idea and created mvaldes14/gh-actions .

This post focuses on reusable workflows: complete jobs that another workflow calls at the job level. The central repository keeps them under .github/workflows/ .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.