GitHub workflows duplication causing maintenance issues and inconsistencies across Zerocracy repositories

[TarasYurkovskyi]

Currently, the same workflows are defined in at least three Zerocracy repositories:

---

---

---

This creates:

• Extra maintenance work - any change must be repeated in multiple repositories

• Risk of inconsistencies if updates are applied to one repo but not the others

• Difficulty tracking the “source of truth” for workflows

Suggested improvement:

Consolidate these workflows into a central reusable workflow repository or designate one repository as the source of truth and reference it
This will ensure consistent CI/CD across all repositories and is easier for auditing and updates

[TarasYurkovskyi]

@yegor256

[yegor256]

@TarasYurkovskyi how exactly we can "consolidate" them? To my knowledge, every GitHub repo must have its own set of CI workflows (YAML files). What do I miss?

[TarasYurkovskyi]

@yegor256 GitHub Actions supports reusable workflows, which allows one repository to reference and execute workflows defined in another repository - https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows

https://docs.github.com/en/actions/how-tos/reuse-automations/share-with-your-organization

IMO, the best solution will be to create the new repo containing all workflows used in multiple repos (or just make one repository jobs as the source of truth ).
Make those workflows reusable using the workflow_call trigger

In any repo that needs the workflow, just reference it like this:

jobs:
  bashate:
    uses: zerocracy-workflows/workflows/.github/workflows/bashate.yml@master

The calling repo doesn’t need to contain any workflow logic itself - it just executes the shared workflow
Updates to the workflow happen once centrally, automatically applied in all repos that use it

[0crat]

@TarasYurkovskyi Thanks for reporting a new bug! According to our work policy, you've earned +18 points as your bonus for helping improve our project quality. By reporting bugs, you actively contribute to making our codebase better. If you find anything else in the repository that doesn't look as good as you might expect, do not hesitate to report it—every accepted bug report earns you the same 18 points reward. Your running balance is +36; don't forget to check your Zerocracy balance too.