Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#1: validate required workflows usage across repositories #1

Open
tlamonthezie opened this issue Sep 17, 2024 · 0 comments · May be fixed by #6
Open

#1: validate required workflows usage across repositories #1

tlamonthezie opened this issue Sep 17, 2024 · 0 comments · May be fixed by #6
Assignees
Labels
enhancement New feature or request

Comments

@tlamonthezie
Copy link
Collaborator

tlamonthezie commented Sep 17, 2024

Create a workflow verifying (automatically using a CRON) that all other repositories in the Github DARMA organization correctly call the required workflows

  • action-git-diff-check.yml
  • check-commit-format.yml
  • check-pr-fixes-issue.yml
  • find-trailing-whitespace.yml
  • find-unsigned-commits.yml

The idea is to check that each repository contains these yaml files under the .github/workflows directory. And if not then generate an error message to say which repository is not compliant and for which file.

Some workflows might have custom arguments (e.g. find-trailing-whitespace excluded files) so in those cases we might to test the file name and that the use: [workflow] is called. In other strict cases we have to check that files are exactly as initial files (we can compare with files in this repository).

@tlamonthezie tlamonthezie self-assigned this Sep 17, 2024
@tlamonthezie tlamonthezie changed the title #1: check that repositories correctly implement the basic required workflows #1: validate required workflows usage Sep 17, 2024
@tlamonthezie tlamonthezie changed the title #1: validate required workflows usage #1: validate required workflows usage across repositories Sep 17, 2024
tlamonthezie added a commit that referenced this issue Sep 18, 2024
@tlamonthezie tlamonthezie added the enhancement New feature or request label Sep 20, 2024
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 6, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 7, 2025
cwschilly added a commit that referenced this issue Jan 8, 2025
cwschilly added a commit that referenced this issue Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant