summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarolyn Van Slyck <carolyn.vanslyck@microsoft.com>2018-07-20 15:27:20 -0500
committerCarolyn Van Slyck <carolyn.vanslyck@microsoft.com>2018-07-20 15:27:20 -0500
commit52506cd95c8cd836969731473c6b05b8a2ebd12d (patch)
tree0d24784d9033fb5370192376d2e4d9838c8e5f4c
parentbe79cf27855608b3ed7c9e123b8f1fb6469bd3b9 (diff)
Don't explictly call out label names
We are in the middle of a migration to prow and the label itself doesn't really matter
-rw-r--r--sig-service-catalog/charter.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/sig-service-catalog/charter.md b/sig-service-catalog/charter.md
index b7f63e18..8cc5d768 100644
--- a/sig-service-catalog/charter.md
+++ b/sig-service-catalog/charter.md
@@ -161,8 +161,7 @@ roles. We do not have the Tech Lead role, and have a honorary Emeritus Chair rol
- While everyone is encouraged to contribute to the discussion of any topic,
ultimately any changes made to the codebase must be approved by the
maintainers.
-- Pull requests are required to have at least 2 maintainers approve them using
- the `LGTM 1` and `LGTM 2` labels.
+- Pull requests are required to have at least 2 maintainers approve them.
- Pull requests that are labeled with `do-not-merge/hold` or have an on-going
discussion must not be merged until all concerns are addressed.
- Disagreements are resolved via lazy consensus. In the event that a common