Browse files

meta: allow vague objections to be dismissed

Explicitly allow vague objections to change requests to
be dismissed if requests for clarification go unanswered

PR-URL: #15233
Reviewed-By: Gibson Fahnestock <>
Reviewed-By: Colin Ihrig <>
Reviewed-By: Jan Krems <>
Reviewed-By: Ryan Graham <>
Reviewed-By: Ali Ijaz Sheikh <>
Reviewed-By: Anna Henningsen <>
Reviewed-By: Refael Ackermann <>
Reviewed-By: Timothy Gu <>
Reviewed-By: Michaël Zasso <>
Reviewed-By: Yuta Hiroto <>
Reviewed-By: Matteo Collina <>
Reviewed-By: Ron Korving <>
Reviewed-By: Tobias Nießen <>
Reviewed-By: Michael Dawson <>
Reviewed-By: Sakthipriyan Vairamani <>
  • Loading branch information...
jasnell authored and MylesBorins committed Sep 6, 2017
1 parent 92f41e5 commit 93ca2f78c61ecd49d8b36649e65fb49ca6459e54
Showing with 6 additions and 0 deletions.
  1. +6 −0
@@ -94,6 +94,12 @@ All pull requests that modify executable code should be subjected to
continuous integration tests on the
[project CI server](
If any Collaborator objects to a change *without giving any additional
explanation or context*, and the objecting Collaborator fails to respond to
explicit requests for explanation or context within a reasonable period of
time, the objection may be dismissed. Note that this does not apply to
objections that are explained.
#### Useful CI Jobs
* [`node-test-pull-request`](

0 comments on commit 93ca2f7

Please sign in to comment.