generated from cloudposse-github-actions/composite-template
-
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
58 additions
and
4 deletions.
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Use this file to define individuals or teams that are responsible for code in a repository. | ||
# Read more: <https://help.github.com/articles/about-codeowners/> | ||
# | ||
# Order is important: the last matching pattern has the highest precedence | ||
|
||
# These owners will be the default owners for everything | ||
* @cloudposse/engineering @cloudposse/contributors | ||
|
||
# Cloud Posse must review any changes to Makefiles | ||
**/Makefile @cloudposse/engineering | ||
**/Makefile.* @cloudposse/engineering | ||
|
||
# Cloud Posse must review any changes to GitHub actions | ||
.github/* @cloudposse/engineering | ||
|
||
# Cloud Posse must review any changes to standard context definition, | ||
# but some changes can be rubber-stamped. | ||
**/*.tf @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers | ||
README.yaml @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers | ||
README.md @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers | ||
docs/*.md @cloudposse/engineering @cloudposse/contributors @cloudposse/approvers | ||
|
||
# Cloud Posse Admins must review all changes to CODEOWNERS or the mergify configuration | ||
.github/mergify.yml @cloudposse/admins | ||
.github/CODEOWNERS @cloudposse/admins |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
name: Validate Codeowners | ||
on: | ||
workflow_dispatch: | ||
|
||
pull_request: | ||
|
||
jobs: | ||
validate-codeowners: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: "Checkout source code at current commit" | ||
uses: actions/checkout@v2 | ||
- uses: mszostok/[email protected] | ||
if: github.event.pull_request.head.repo.full_name == github.repository | ||
name: "Full check of CODEOWNERS" | ||
with: | ||
# For now, remove "files" check to allow CODEOWNERS to specify non-existent | ||
# files so we can use the same CODEOWNERS file for Terraform and non-Terraform repos | ||
# checks: "files,syntax,owners,duppatterns" | ||
checks: "syntax,owners,duppatterns" | ||
owner_checker_allow_unowned_patterns: "false" | ||
# GitHub access token is required only if the `owners` check is enabled | ||
github_access_token: "${{ secrets.PUBLIC_REPO_ACCESS_TOKEN }}" | ||
- uses: mszostok/[email protected] | ||
if: github.event.pull_request.head.repo.full_name != github.repository | ||
name: "Syntax check of CODEOWNERS" | ||
with: | ||
checks: "syntax,duppatterns" | ||
owner_checker_allow_unowned_patterns: "false" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters