8 Commits
Author SHA1 Message Date
Jon Ross-PerkinsandDana Jansens f27ccbf76e Add CODEOWNERS for review assignment (#6153)
This disables the autoassign action so that the codeowners approach can
be tested without interference.

Trying this out because it might be a path for vacation handling. See
[GitHub
docs](https://docs.github.com/en/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)
and
[#infra](https://discord.com/channels/655572317891461132/707150492370862090/1422985757311635620)

---------

Co-authored-by: Dana Jansens <danakj@orodu.net>
2025-10-01 17:50:53 +00:00
Jon Ross-Perkins 142a48e204 rm CODEOWNERS (#1399)
Versus #1367 which approved this in principle, this is the actual removal (I've updated write permissions in GH now).
2022-07-15 18:40:57 -07:00
Jon Meow fa984743bf Update CODEOWNERS for the carbon-leads switch (#458) 2021-04-13 20:58:10 -07:00
Jon Meow e3f922b977 Consolidate ownership for easier reviews (#256)
Add implementation-team to more dirs, drop infra-team
2021-02-04 10:48:33 -08:00
Jon Meow 0281274d9c toolchain-team -> implementation-team (#249) 2021-02-03 16:28:19 -08:00
Chandler CarruthandJon Meow 751ee936a8 Update our CODEOWNERS based on the merging repos. (#206)
We've already started the merge, but this tries to lay out a reasonable
trajectory for things to move along.

Co-authored-by: Jon Meow <46229924+jonmeow@users.noreply.github.com>
2020-12-08 01:36:28 -08:00
Jon Meow a768b0ee19 Adjust copyrights based on carbon-project-tools/#3 (#171) 2020-10-09 10:18:06 -07:00
Chandler Carruth 630311c6ae Create code review guidelines (#42)
Carbon needs a strong code review process to handle code (and other)
changes that are not significant proposals. This attempts to provide
clear guidance on the process, structure, and scope of code review.
It also gives detailed guidance on how to effectively do code review
for both reviewers and authors.

This proposal was accepted on 2020-08-04.
2020-08-27 02:05:40 -07:00