diff options
| author | Emilio Jesus Gallego Arias | 2019-03-01 12:20:10 +0100 |
|---|---|---|
| committer | Emilio Jesus Gallego Arias | 2019-03-01 12:20:10 +0100 |
| commit | ebdcaa393b1f332ad917b33bf9d7a222d3faa7c4 (patch) | |
| tree | 2a934fdfde29adbddc74f0587e038e159c429cb2 /dev/doc | |
| parent | 2eb10f5a34ddb378051db9e4df943956ac0e3849 (diff) | |
| parent | b46b8cbe886ea1e06377843134e9c588394acc5f (diff) | |
Merge PR #9610: Fix #9110: mention check-owners-pr.sh
Ack-by: SkySkimmer
Ack-by: Zimmi48
Reviewed-by: ejgallego
Ack-by: vbgl
Diffstat (limited to 'dev/doc')
| -rw-r--r-- | dev/doc/MERGING.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/dev/doc/MERGING.md b/dev/doc/MERGING.md index 5705857d76..3f1b470878 100644 --- a/dev/doc/MERGING.md +++ b/dev/doc/MERGING.md @@ -37,6 +37,9 @@ When maintainers receive a review request, they are expected to: REVIEWERS(*) have approved the PR, the assignee is expected to follow the merging process described below. +To know what files you are a code owner of in a large PR, you can run +`dev/tools/check-owners-pr.sh xxxx`. Results are unfortunately imperfect. + When a PR received lots of comments or if the PR has not been opened for long and the assignee thinks that some other developers might want to comment, it is recommended that they announce their intention to merge and wait a full |