generated from MITLibraries/python-cli-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Add CODEOWNERS and update dependencies #46
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,20 @@ | ||
| # CODEOWNERS file (from GitHub template at | ||
| # https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) | ||
| # Each line is a file pattern followed by one or more owners. | ||
|
|
||
| ################################################################################ | ||
| # These owners will be the default owners for everything in the repo. This is commented | ||
| # out in favor of using a team as the default (see below). It is left here as a comment | ||
| # to indicate the primary expert for this code. | ||
| # * @ghukill | ||
|
|
||
| # Teams can be specified as code owners as well. Teams should be identified in | ||
| # the format @org/team-name. Teams must have explicit write access to the | ||
| # repository. | ||
| * @mitlibraries/dataeng | ||
| /.github/* @mitlibraries/infraeng | ||
| /.github/ci.yml @mitlibraries/dataeng | ||
|
|
||
| # We set the senior engineer in the team as the owner of the CODEOWNERS file as | ||
| # a layer of protection for unauthorized changes. | ||
| /.github/CODEOWNERS @ghukill | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ghukill It might be worth adding a line specifying that the workflows should be linked to InfraEng..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cabutlermit - Happy to add, but do you think it's more true for this repository than others? does adding it here imply we should be adding InfraEng globally to
CODEOWNERSfiles?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha! I should have been more specific and more detailed in my comment. I'm picturing lines like this in
CODEOWNERS, at least in this repo and maybe in other repos that have GHA workflows that publish apps to ECR in AWS.Or, maybe this would do it (I think that later lines override earlier lines):
That way, if anyone ever makes changes to those workflow files and PR's those changes, InfraEng will automatically get tagged for review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cabutlermit - Ahhhhh! Makes sense, love it. Thanks for the clarification. I don't have very strong
CODEOWNERSintuition yet, but appreciating this per-file-pattern approach and the implications there. Will add.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New commit here: 88dc80d. Review re-requested.