From f4d850e16803dfd2ea4ffc7399b41cede688bba6 Mon Sep 17 00:00:00 2001
From: Tobias Bosch
Date: Mon, 9 Dec 2013 17:30:43 -0800
Subject: docs(TRIAGING): Labels cla yes/no are automatically set

The labels are set by a script and
should not be set manually any more.
---
 TRIAGING.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/TRIAGING.md b/TRIAGING.md
index ec7ac6e8..3179a669 100644
--- a/TRIAGING.md
+++ b/TRIAGING.md
@@ -10,6 +10,13 @@ The labels are used later on for planning releases.
     * these tags can be used for labeling a closed issue/PR with a reason why it was closed. (we can add reasons as we need them, right there are only a few rejection reasons. it doesn't make sense to label issues that were fixed or prs that were merged)
 
 
+## Automatic processing ##
+
+We have automatic tools (e.g. Mary Poppins) that automatically add comments / labels to issues and PRs.
+The following is done automatically and should not be done manually:
+
+* Label "cla: yes" or "cla: no" for pull requests
+
 ## Process ##
 
 1. Open list of [non triaged issues](https://github.com/angular/angular.js/issues?direction=desc&milestone=none&page=1&sort=created&state=open)
@@ -46,8 +53,6 @@ The labels are used later on for planning releases.
     * large - changes to many components in angular or any changes to $compile, ngRepeat or other "fun" components
 1. Label "PRs welcome" for "GH: issue"
     * if complexity is small or medium and the problem as well as solution are well captured in the issue
-1. Label "cla: yes" for "GH: PR": 
-    * otherwise prompt the contributor to sign the CLA
 1. Label "origin: google" for issues from Google
 1. Label "high priority" for security issues, major performance regressions or memory leaks
 
-- 
cgit v1.2.3