Centralize GitHub Workflows

[ialejandro]

The idea behind this structure is to maintain a centralized repository where reusable workflows are stored, promoting consistency and reducing duplication across multiple projects. Each directory under .github/workflows represents a technology or tool (e.g., Helm, Ansible, Docker) and contains specific workflows (e.g., linting, deployment, testing). Common workflows that are applicable to multiple technologies can be stored in a common directory.

Directories

Here are some examples of how you might structure the directories:

.github/
└── workflows/
    ├── helm/
    │   ├── lint.yml
    │   ├── deploy.yml
    │   └── test.yml
    ├── ansible/
    │   ├── lint.yml
    │   ├── deploy.yml
    │   └── test.yml
    ├── docker/
    │   ├── build.yml
    │   ├── push.yml
    │   └── scan.yml
    └── common/
        ├── notify-slack.yml
        ├── setup-env.yml
        └── run-tests.yml

Another solution:

.github/
└── workflows/
    ├── templates/
    │   ├── helm/
    │   │   ├── lint-template.yml
    │   │   ├── deploy-template.yml
    │   │   └── test-template.yml
    │   ├── ansible/
    │   │   ├── lint-template.yml
    │   │   ├── deploy-template.yml
    │   │   └── test-template.yml
    │   └── docker/
    │       ├── build-template.yml
    │       ├── push-template.yml
    │       └── scan-template.yml
    ├── helm/
    │   ├── lint.yml
    │   ├── deploy.yml
    │   └── test.yml
    ├── ansible/
    │   ├── lint.yml
    │   ├── deploy.yml
    │   └── test.yml
    ├── docker/
    │   ├── build.yml
    │   ├── push.yml
    │   └── scan.yml
    └── common/
        ├── notify-slack.yml
        ├── setup-env.yml
        └── run-tests.yml

More info.

• Avoid duplication
• Reuse workflows
• Workflows templates