prepare for branch move master -> main

dkgi · facebook-github-bot · commit 8c4fb603e41d · 2021-08-04T16:40:29.000-07:00
Summary: Hoping I got all relevant references.

Reviewed By: arthaud

Differential Revision: D30115011

fbshipit-source-id: 69535e269af6061c78f23f0f0728a8962d3da36a
diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
@@ -2,9 +2,9 @@ name: lint
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
   workflow_dispatch:
 
diff --git a/.github/workflows/publish_website.yml b/.github/workflows/publish_website.yml
@@ -1,9 +1,9 @@
-name: publish website  
-          
+name: publish website
+
 on:
   push:
-    branches: [ master ]
-    
+    branches: [ main ]
+
   workflow_dispatch:
 
 jobs:
diff --git a/.github/workflows/pyre.yml b/.github/workflows/pyre.yml
@@ -2,9 +2,9 @@ name: pyre
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
   workflow_dispatch:
 
diff --git a/.github/workflows/pysa.yml b/.github/workflows/pysa.yml
@@ -2,9 +2,9 @@ name: pysa
 
 on:
   push:
-    branches: [ test-2, master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
   workflow_dispatch:
 
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
@@ -2,9 +2,9 @@ name: tests
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 
   workflow_dispatch:
 
diff --git a/CONTRIBUTING.es.md b/CONTRIBUTING.es.md
@@ -9,7 +9,7 @@ posible.
 
 Aceptamos activamente sus solicitudes de extracción.
 
-1. Fork el repositorio y crear su rama de `master`.
+1. Fork el repositorio y crear su rama de `main`.
 2. Si ha agregado un código que debe probarse, agregue pruebas.
 3. Si ha cambiado las APIs, actualice la documentación.
 4. Asegúrese de que el conjunto de pruebas pase (consulte [la siguiente sección](#ejecución-de-pruebas)).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -7,7 +7,7 @@ possible.
 ## Pull Requests
 We actively welcome your pull requests.
 
-1. Fork the repo and create your branch from `master`.
+1. Fork the repo and create your branch from `main`.
 2. If you've added code that should be tested, add tests.
 3. If you've changed APIs, update the documentation.
 4. Ensure the test suite passes (please see [the following section](#running-tests)).
diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/facebook/pyre-check/master/logo.png">
+  <img src="https://raw.githubusercontent.com/facebook/pyre-check/main/logo.png">
 </p>
 
 Pyre is a performant type checker for Python compliant with [PEP 484](https://www.python.org/dev/peps/pep-0484/). Pyre can analyze codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code.
diff --git a/documentation/pysa_tutorial/exercise3/README.md b/documentation/pysa_tutorial/exercise3/README.md
@@ -16,9 +16,9 @@ standard library, and many open source libraries. Since the previous exercises
 already covered those concepts, from this exercise forward we will be relying on
 pre-written sources, sinks, and rules where we can. You can look at the
 collection of pre-written
-[`taint.config`](https://github.com/facebook/pyre-check/blob/master/stubs/taint/taint.config)
+[`taint.config`](https://github.com/facebook/pyre-check/blob/main/stubs/taint/taint.config)
 and `*.pysa` files in the
-[`stubs/taint`](https://github.com/facebook/pyre-check/tree/master/stubs/taint)
+[`stubs/taint`](https://github.com/facebook/pyre-check/tree/main/stubs/taint)
 folder in this repository. If you are curious about what changed between this
 and the previous exercise to allow us to take advantage of those pre-written
 files, compare the `.pyre_configuration` files.
diff --git a/documentation/website/docs/formal/python_semantic/Expression.v b/documentation/website/docs/formal/python_semantic/Expression.v
@@ -32,7 +32,7 @@ Inductive unary_operator :=
 
 (** * Expressions
     More will be added later. See
-    https://github.com/facebook/pyre-check/blob/master/ast/expression.mli#L216
+    https://github.com/facebook/pyre-check/blob/main/ast/expression.mli#L216
 *)
 Inductive t: Set :=
   | BooleanOperator: forall (left: t) (op: boolean_operator) (right: t), t
@@ -84,7 +84,7 @@ Proof.
 induction l as [ | hd tl hi]; simpl in *; [ now idtac | ].
 now rewrite hi.
 Qed.
- 
+
 Coercion to_list: tlist >-> list.
 End ListHelpers.
 (* end hide *)
diff --git a/documentation/website/docs/formal/python_semantic/Statement.v b/documentation/website/docs/formal/python_semantic/Statement.v
@@ -6,7 +6,7 @@ Require Pyre.Typ.
 (** * Statements
 
   More will be added later on. See
-  https://github.com/facebook/pyre-check/blob/master/ast/statement.mli#L331
+  https://github.com/facebook/pyre-check/blob/main/ast/statement.mli#L331
 *)
 Inductive t : Set :=
   | Assign: forall (target: Lvalue.t)
@@ -25,13 +25,13 @@ Inductive t : Set :=
   | Nonlocal: list string -> t
   | Pass: t
   | While: forall (test: Expression.t) (body orelse: t), t
-  | Seq : forall (st next : t), t 
+  | Seq : forall (st next : t), t
   | Return: forall (ret: Expression.t), t
 .
 
 Fixpoint to_seq (statements: list t) : t :=
-  match statements with 
-  | nil => Pass 
-  | hd :: nil => hd 
+  match statements with
+  | nil => Pass
+  | hd :: nil => hd
   | hd :: tl => Seq hd (to_seq tl)
   end.
diff --git a/documentation/website/docs/pysa_advanced.md b/documentation/website/docs/pysa_advanced.md
@@ -261,7 +261,7 @@ method.
 
 By default, Pysa skips overrides on some functions that are typically
 problematic. You can find the full list of default-skipped functions in
-[`stubs/taint/skipped_overrides.pysa`](https://github.com/facebook/pyre-check/blob/master/stubs/taint/skipped_overrides.pysa)
+[`stubs/taint/skipped_overrides.pysa`](https://github.com/facebook/pyre-check/blob/main/stubs/taint/skipped_overrides.pysa)
 
 ## Limit the trace length for better signal and performance
 
diff --git a/documentation/website/docs/pysa_basics.md b/documentation/website/docs/pysa_basics.md
@@ -66,7 +66,7 @@ file is a JSON document which stores definitions for *sources*, *sinks*, *featur
 and *rules* (discussed below). The `.pysa` files are model files (also discussed
 below) which annotate your code with the *sources*, *sinks*, and *features* defined in
 your `taint.config` file. Examples of these files can be found in the [Pyre
-repository](https://github.com/facebook/pyre-check/tree/master/stubs/taint).
+repository](https://github.com/facebook/pyre-check/tree/main/stubs/taint).
 
 These files live in the directory configured by `taint_models_path` in your
 `.pyre_configuration` file. Any `.pysa` file found in this folder will be parsed
diff --git a/documentation/website/docs/pysa_precollectors.md b/documentation/website/docs/pysa_precollectors.md
@@ -10,7 +10,7 @@ Some sources and sinks may be too numerous or too rapidly changing for defining
 them statically to be practical. For these scenarios, Pysa has the concept of
 model generators, which can generate taint models by reading the project's source code before static analysis is
 started. The current set of model generators is stored in
-[`tools/generate_taint_models`](https://github.com/facebook/pyre-check/tree/master/tools/generate_taint_models)
+[`tools/generate_taint_models`](https://github.com/facebook/pyre-check/tree/main/tools/generate_taint_models)
 within the pyre-check repository.
 
 Pysa now has the concept of a [Model DSL](pysa_model_dsl.md), which supports
@@ -25,15 +25,15 @@ configured for Django, meaning it has to import (and implicitly run) the file
 you use to configure routing. The recommended way to run model generators is to set
 up a small script within your repository that can run within the virtual
 environment for your project. **[This tutorial
-exercise](https://github.com/facebook/pyre-check/tree/master/documentation/pysa_tutorial/exercise5)
+exercise](https://github.com/facebook/pyre-check/tree/main/documentation/pysa_tutorial/exercise5)
 provides an example of how to setup and use model generators.**
 
 ## Example Model Generators
 
 The set of model generators is always changing, but below are some examples of
 model generators which are currently provided out of the box with Pysa.
 
-### [`RESTApiSourceGenerator`](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/get_REST_api_sources.py)
+### [`RESTApiSourceGenerator`](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/get_REST_api_sources.py)
 
 This model generator is intended to taint all arguments to [Django view
 functions](https://docs.djangoproject.com/en/2.2/topics/http/views/) as
@@ -42,7 +42,7 @@ user-controlled data as arguments separate from the `HttpRequest` parameter,
 such as when [capturing values from the request
 path](https://docs.djangoproject.com/en/2.2/topics/http/urls/#example).
 
-### [`ExitNodeGenerator`](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/get_exit_nodes.py)
+### [`ExitNodeGenerator`](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/get_exit_nodes.py)
 
 This generator is intended to taint all data returned from [Django view
 functions](https://docs.djangoproject.com/en/2.2/topics/http/views/) as
@@ -51,14 +51,14 @@ functions to return raw python types, rather than `HttpResponse` objects. Note
 that you do not need this generator if you always construct `HttpResponse`
 objects, because they are already annotated as `ReturnedToUser` sinks.
 
-### [`GraphQLSourceGenerator`](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/get_graphql_sources.py)
+### [`GraphQLSourceGenerator`](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/get_graphql_sources.py)
 
 This model generator is similar to the `RESTApiSourceGenerator` and
 `ExitNodeGenerator` discussed above, but it is intended to generate models with
 `UserControlled` and `ReturnedToUser` annotations for graphene-style GraphQL
 `resolver` functions.
 
-### [`AnnotatedFreeFunctionWithDecoratorGenerator`](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/get_annotated_free_functions_with_decorator.py)
+### [`AnnotatedFreeFunctionWithDecoratorGenerator`](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/get_annotated_free_functions_with_decorator.py)
 
 This model generator provides general purpose functionality to annotate all free
 functions which have a given decorator. The annotations can be used to mark any
@@ -72,7 +72,7 @@ rule.
 ## Writing Model Generators
 
 All model generator code lives in
-[`tools/generate_taint_models`](https://github.com/facebook/pyre-check/tree/master/tools/generate_taint_models)
+[`tools/generate_taint_models`](https://github.com/facebook/pyre-check/tree/main/tools/generate_taint_models)
 within the pyre-check repository.
 
 
@@ -84,9 +84,9 @@ provides an example of how to add a new model generator.
 The basic workflow is:
 
 1. Create a new file under `generate_taint_models` of the form `get_<pattern of model>`.
-1. Write a class that inherits from [ModelGenerator](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/model_generator.py).
+1. Write a class that inherits from [ModelGenerator](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/model_generator.py).
 1. Collect all the callables you're interested in modeling via `gather_functions_to_model`.
-1. Convert the callables you've collected into models. The [CallableModel](https://github.com/facebook/pyre-check/blob/master/tools/generate_taint_models/model.py) class is a convenience that pretty prints things in the right way - you just need to specify what kind of taint the parameters and return value should have, specify the callable to model, and call generate().
+1. Convert the callables you've collected into models. The [CallableModel](https://github.com/facebook/pyre-check/blob/main/tools/generate_taint_models/model.py) class is a convenience that pretty prints things in the right way - you just need to specify what kind of taint the parameters and return value should have, specify the callable to model, and call generate().
 1. Write unit tests ([example](https://github.com/facebook/pyre-check/blob/922410239404aa436691754402b0c3db68c5a46f/tools/generate_taint_models/tests/get_annotated_free_functions_with_decorator_test.py)).
 1. Import your new class in the `__init__` file ([example](https://github.com/facebook/pyre-check/blob/922410239404aa436691754402b0c3db68c5a46f/tools/generate_taint_models/__init__.py#L7)).
 
diff --git a/documentation/website/docs/pysa_running.md b/documentation/website/docs/pysa_running.md
@@ -6,7 +6,7 @@ sidebar_label: Running Pysa
 
 This page walks you through the basics of running Pysa. If you want exercises to
 walk you through using Pysa's more advanced features, check out [this
-tutorial](https://github.com/facebook/pyre-check/tree/master/documentation/pysa_tutorial).
+tutorial](https://github.com/facebook/pyre-check/tree/main/documentation/pysa_tutorial).
 
 ## Setup
 
diff --git a/documentation/website/docusaurus.config.js b/documentation/website/docusaurus.config.js
@@ -50,7 +50,7 @@ module.exports = {
           // Where to point users when they click "Edit this page"
           editUrl: fbContent({
             internal: 'https://www.internalfb.com/intern/diffusion/FBS/browse/master/fbcode/tools/pyre/documentation/website/',
-            external: 'https://github.com/facebook/pyre-check/tree/master/documentation/website'
+            external: 'https://github.com/facebook/pyre-check/tree/main/documentation/website'
           }),
         },
         theme: {
diff --git a/pysa_tutorial/README.md b/pysa_tutorial/README.md
@@ -1,3 +1,3 @@
 # Pysa Tutorial
 
-This tutorial has moved to [documentation/pysa_tutorial](https://github.com/facebook/pyre-check/tree/master/documentation/pysa_tutorial/).
+This tutorial has moved to [documentation/pysa_tutorial](https://github.com/facebook/pyre-check/tree/main/documentation/pysa_tutorial/).
