puppetlabs/vmpooler
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler.git synced 2026-01-26 01:58:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Remove DIO as codeowners

Browse source
This commit is contained in:
Jake Spain 2022-08-26 09:34:27 -04:00
parent 9fb9d93c03
commit e2b5e903ad
No known key found for this signature in database
GPG key ID: BC1C4DA0A085E113
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
CODEOWNERS
View file

@ -1,10 +1,10 @@
# This will cause DIO and RE to be assigned review of any opened PRs against # This will cause RE to be assigned review of any opened PRs against
# the branches containing this file. # the branches containing this file.
# See https://help.github.com/en/articles/about-code-owners for info on how to # See https://help.github.com/en/articles/about-code-owners for info on how to
# take ownership of parts of the code base that should be reviewed by another # take ownership of parts of the code base that should be reviewed by another
# team. # team.
# DIO and RE will be the default owners for everything in the repo. # RE will be the default owners for everything in the repo.
* @puppetlabs/dio @puppetlabs/release-engineering * @puppetlabs/release-engineering

2
CONTRIBUTING.md
View file

@ -64,7 +64,7 @@ the new documentation or comments added.
* Submit a pull request to the repository in the puppetlabs organization. * Submit a pull request to the repository in the puppetlabs organization.
* Update your Jira ticket to mark that you have submitted code and are ready for it to be reviewed (Status: Ready for Merge). * Update your Jira ticket to mark that you have submitted code and are ready for it to be reviewed (Status: Ready for Merge).
* Include a link to the pull request in the ticket. * Include a link to the pull request in the ticket.
* The Puppet DIO team looks at Pull Requests on a regular basis. * The Puppet Release Engineering team looks at Pull Requests on a regular basis.
* After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity. * After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.
## Additional Resources ## Additional Resources