Add CODEOWNERS usage details#7784
Conversation
- Usage of @ghost to exclude directories - Changing files under an author's ownership - Appointing more than one CODEOWNER
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
|
@sidletsky Thanks so much for opening an issue and a PR! I'll get this triaged for review ⚡ |
|
Thanks for this pull request ✨ I've asked a few questions about these changes on #7783 and will review the pull request once we are clear on what changes to make to this article. |
felicitymay
left a comment
There was a problem hiding this comment.
Hi @sidletsky - thank you for your updates to this PR 💖
I've suggested some changes, but they're fairly small things. Once I've merged those changes, this should be ready to merge. Thank you so much for taking the time to raise this problem, to discuss the best way to make the behavior clear, and to improve the docs for other users. ✨
|
👋🏻 I'm not sure if you'll have seen these or not, but just in case. I have just deleted a couple of comments on your original changes that I wrote but didn't submit. It looked as if they reappeared as part of the review of the current content. Apologies for any confusion. |
…ating-a-repository-on-github/about-code-owners.md
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes #7783
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):