|
1 | 1 | # mcaf-github-workflows |
2 | 2 |
|
3 | | -Repository for centralized reusable Github workflows. |
| 3 | +Repository to synchronize GitHub workflows and repository files. |
4 | 4 |
|
5 | | -## Create workflows |
| 5 | +## Adding Repositories |
6 | 6 |
|
7 | | -Create or modify a yaml file in [.github/workflows/](.github/workflows/). Also update README.md with details about your workflow and remember that this is a public repository. |
| 7 | +To add your repository to the sync: |
8 | 8 |
|
9 | | -Push your changes to a branch. Once you are done with all your changes, open a PR. |
| 9 | +- Add your repository to `REPOSITORIES` in the YAML file: `.github/workflows/workflow-synchronization.yaml`. |
| 10 | + |
| 11 | +## Updating & Creating Workflows |
| 12 | + |
| 13 | +To create or modify a workflow: |
| 14 | + |
| 15 | +- Add or update a YAML file in the [`.github/workflows/`](.github/workflows/) directory. |
| 16 | +- Update the `README.md` with details about your workflow. |
| 17 | +- Ensure that your changes align with best practices and repository conventions. |
| 18 | +- Push your changes to a branch and open a Pull Request (PR) once all modifications are complete. |
10 | 19 |
|
11 | 20 | ## Workflows |
12 | 21 |
|
| 22 | +### Label Synchronization |
| 23 | + |
| 24 | +Ensures that the repository contains the required GitHub labels. |
| 25 | + |
13 | 26 | ### PR Validation |
14 | 27 |
|
15 | | -Verifies the PR has the required labels and proper title set. |
| 28 | +Verifies that a PR has the required labels and a properly formatted title before merging. |
16 | 29 |
|
17 | 30 | ### Release Drafter |
18 | 31 |
|
19 | | -Creates a drafted release based on the labels, title and description of the PR. |
| 32 | +Automatically drafts a release based on PR labels, title, and description, simplifying the release process. |
20 | 33 |
|
21 | 34 | ### Terraform Validation |
22 | 35 |
|
23 | | -Verifies the terraform code adheres to best practises and has secure defaults set. |
| 36 | +Validates Terraform code to ensure adherence to best practices and security standards. |
| 37 | + |
| 38 | +### Changelog Update |
| 39 | + |
| 40 | +Automatically updates `CHANGELOG.md` when a new release is published, keeping version history up to date. |
| 41 | + |
| 42 | +## Repository Files |
| 43 | + |
| 44 | +### `.gitignore` |
| 45 | + |
| 46 | +Maintains consistency with our module structure and pre-commit setup. |
| 47 | +_Note: OS-specific or IDE-specific ignores are excluded; users should configure these in their global `.gitignore` file._ |
| 48 | + |
| 49 | +### `LICENSE` |
| 50 | + |
| 51 | +Ensures that all repositories include the Apache License Version 2.0 for open-source compliance. |
| 52 | + |
| 53 | +### `CONTRIBUTING.md` |
| 54 | + |
| 55 | +Provides clear guidelines on how to contribute, ensuring a structured and efficient collaboration process. |
| 56 | + |
| 57 | +### `.pre-commit-config.yaml` |
| 58 | + |
| 59 | +Includes a pre-commit configuration to streamline local development by catching simple issues before creating a PR. |
| 60 | + |
| 61 | +### Pull Request Template |
| 62 | + |
| 63 | +Standardizes PR submissions by guiding contributors to provide essential details, improving the review process. |
24 | 64 |
|
25 | | -### Update changelog |
| 65 | +### Issue Templates |
26 | 66 |
|
27 | | -Updates the CHANGELOG.md when a release gets published. |
| 67 | +Defines structured templates for bug reports, feature requests, and general questions to ensure clear and complete issue descriptions. |
0 commit comments