Reversion: new-ruleset in labeller

Hainish · Hainish · commit 2040db451b8b · 2017-03-30T12:59:13.000-07:00
diff --git a/utils/labeller/README.md b/utils/labeller/README.md
@@ -8,8 +8,6 @@ This compares the open PR requests that have ruleset changes to the Alexa top 1M
 4. `top-100k`
 5. `top-1m`
 
-The label `new-ruleset` will be applied if the PR includes a completely new ruleset.
-
 This will work for admins of HTTPS Everywhere that generate a [GitHub token](https://github.com/settings/tokens).
 
 ## Setup
diff --git a/utils/labeller/index.js b/utils/labeller/index.js
@@ -133,7 +133,6 @@ function github_process_prs(res, pr_cb){
             }
 
             var file_fetches = [];
-            var newRuleset;
 
             // Out of the list of files for this PR, figure out the minimum Alexa ranking for each
             _.each(files, function(file){
@@ -155,24 +154,9 @@ function github_process_prs(res, pr_cb){
                     }
                   });
                 });
-                
-                if (!fs.existsSync('../../' + file.filename)) {
-                  newRuleset = true;
-                }
               }
             });
 
-            if (newRuleset) {
-              console.log("Applying label `new-ruleset` to PR: " + pull_request.number);
-              
-              github.issues.addLabels(_.extend(httpse, {
-                number: pull_request.number,
-                body: ['new-ruleset']
-              }), function(err, res) {
-                if (err) console.log(err);
-              });
-            }
-
             async.parallel(file_fetches, function(err, res){
               if(err) pr_cb(err);
 
