Update self reference to use main… 🧙

… instead of master.

Signed-off-by: Vincent Demeester <[email protected]>

DEVELOPMENT.md

@@ -36,12 +36,12 @@ of the technology this project is built on. This project extends Kubernetes (aka
 
 At this point, you may find it useful to return to these `Tekton Pipeline` docs:
 
--   [Tekton Pipeline README](https://github.com/tektoncd/pipeline/blob/master/docs/README.md) -
+-   [Tekton Pipeline README](https://github.com/tektoncd/pipeline/blob/main/docs/README.md) -
     Some of the terms here may make more sense!
 -   Install via
-    [official installation docs](https://github.com/tektoncd/pipeline/blob/master/docs/install.md)
+    [official installation docs](https://github.com/tektoncd/pipeline/blob/main/docs/install.md)
     or continue through [getting started for development](#getting-started)
--   [Tekton Pipeline "Hello World" tutorial](https://github.com/tektoncd/pipeline/blob/master/docs/tutorial.md) -
+-   [Tekton Pipeline "Hello World" tutorial](https://github.com/tektoncd/pipeline/blob/main/docs/tutorial.md) -
     Define `Tasks`, `Pipelines`, and `PipelineResources`, see what happens when
     they are run
 

api_compatibility_policy.md

@@ -20,7 +20,7 @@ The API is considered to consist of:
 - The structure of the [directories created in executing containers by Tekton](docs/tasks.md#reserved-directories)
 - The order that `PipelineResources` declared within a `Task` are applied in
 - The interfaces of the images that are built as part of Tekton Pipelines,
-  i.e. images in [cmd](https://github.com/tektoncd/pipeline/tree/master/cmd) which are used as part of
+  i.e. images in [cmd](https://github.com/tektoncd/pipeline/tree/main/cmd) which are used as part of
   [PipelineResources](docs/resources.md)
 
 This policy is about changes to any of the above facets of the API.
@@ -83,5 +83,5 @@ These changes must be approved by [more than half of the project OWNERS](OWNERS)
 
 ## Deprecated Features
 
-Tekton Pipelines [maintains a list of features that have been deprecated](https://github.com/tektoncd/pipeline/tree/master/docs/deprecations.md)
+Tekton Pipelines [maintains a list of features that have been deprecated](https://github.com/tektoncd/pipeline/tree/main/docs/deprecations.md)
 which includes the earliest date each feature will be removed.

cmd/pullrequest-init/example/README.md

@@ -4,5 +4,5 @@ This directory serves as an example of the pull request payloads you can expect
 from the pull request pipeline resource.
 
 See
-https://github.com/tektoncd/pipeline/blob/master/docs/resources.md#pull-request-resource
+https://github.com/tektoncd/pipeline/blob/main/docs/resources.md#pull-request-resource
 for more documentation.

cmd/pullrequest-init/example/comments/508007084.json

@@ -1,6 +1,6 @@
 {
   "ID": 508007084,
-  "Body": "[APPROVALNOTIFIER] This PR is **APPROVED**\n\nThis pull-request has been approved by: *<a href=\"https://github.com/tektoncd/pipeline/pull/995#pullrequestreview-254634050\" title=\"Approved\">afrittoli</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#issuecomment-506082465\" title=\"Approved\">dlorenc</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#pullrequestreview-257350830\" title=\"LGTM\">vdemeester</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#\" title=\"Author self-approved\">wlynch</a>*\n\nThe full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands).\n\nThe pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)\n\n<details >\nNeeds approval from an approver in each of these files:\n\n- ~~[OWNERS](https://github.com/tektoncd/pipeline/blob/master/OWNERS)~~ [dlorenc,vdemeester]\n\nApprovers can indicate their approval by writing `/approve` in a comment\nApprovers can cancel approval by writing `/approve cancel` in a comment\n</details>\n<!-- META={\"approvers\":[]} -->",
+  "Body": "[APPROVALNOTIFIER] This PR is **APPROVED**\n\nThis pull-request has been approved by: *<a href=\"https://github.com/tektoncd/pipeline/pull/995#pullrequestreview-254634050\" title=\"Approved\">afrittoli</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#issuecomment-506082465\" title=\"Approved\">dlorenc</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#pullrequestreview-257350830\" title=\"LGTM\">vdemeester</a>*, *<a href=\"https://github.com/tektoncd/pipeline/pull/995#\" title=\"Author self-approved\">wlynch</a>*\n\nThe full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands).\n\nThe pull request process is described [here](https://git.k8s.io/community/contributors/guide/owners.md#the-code-review-process)\n\n<details >\nNeeds approval from an approver in each of these files:\n\n- ~~[OWNERS](https://github.com/tektoncd/pipeline/blob/main/OWNERS)~~ [dlorenc,vdemeester]\n\nApprovers can indicate their approval by writing `/approve` in a comment\nApprovers can cancel approval by writing `/approve cancel` in a comment\n</details>\n<!-- META={\"approvers\":[]} -->",
   "Author": {
     "Login": "tekton-robot",
     "Name": "",

cmd/pullrequest-init/example/pr.json

@@ -1,7 +1,7 @@
 {
   "Number": 995,
   "Title": "Add GitHub status updates to Pull Request CRD.",
-  "Body": "This adds support for the GitHub Status API\r\n(https://developer.github.com/v3/repos/statuses/).\r\n\r\nThis accompanies #778 and #895 to complete initial Pull Request support\r\nsupport for GitHub OAuth.\r\n\r\n<!-- 🎉🎉🎉 Thank you for the PR!!! 🎉🎉🎉 -->\r\n\r\n# Changes\r\n\r\nAdds GitHub status fetching and updates to Pull Request CRD.\r\n\r\n# Submitter Checklist\r\n\r\nThese are the criteria that every PR should meet, please check them off as you\r\nreview them:\r\n\r\n- [x] Includes [tests](https://github.com/tektoncd/community/blob/main/standards.md#principles) (if functionality changed/added)\r\n- [x] Includes [docs](https://github.com/tektoncd/community/blob/main/standards.md#principles) (if user facing)\r\n- [x] Commit messages follow [commit message best practices](https://github.com/tektoncd/community/blob/main/standards.md#commit-messages)\r\n\r\n_See [the contribution guide](https://github.com/tektoncd/pipeline/blob/master/CONTRIBUTING.md)\r\nfor more details._\r\n\r\n# Release Notes\r\n\r\n<!--\r\nDoes your PR contain User facing changes?\r\n\r\nIf so, briefly describe them here so we can include this description in the\r\nrelease notes for the next release!\r\n-->\r\n\r\n```\r\nAdds GitHub status fetching and updates to Pull Request CRD.\r\n```\r\n",
+  "Body": "This adds support for the GitHub Status API\r\n(https://developer.github.com/v3/repos/statuses/).\r\n\r\nThis accompanies #778 and #895 to complete initial Pull Request support\r\nsupport for GitHub OAuth.\r\n\r\n<!-- 🎉🎉🎉 Thank you for the PR!!! 🎉🎉🎉 -->\r\n\r\n# Changes\r\n\r\nAdds GitHub status fetching and updates to Pull Request CRD.\r\n\r\n# Submitter Checklist\r\n\r\nThese are the criteria that every PR should meet, please check them off as you\r\nreview them:\r\n\r\n- [x] Includes [tests](https://github.com/tektoncd/community/blob/main/standards.md#principles) (if functionality changed/added)\r\n- [x] Includes [docs](https://github.com/tektoncd/community/blob/main/standards.md#principles) (if user facing)\r\n- [x] Commit messages follow [commit message best practices](https://github.com/tektoncd/community/blob/main/standards.md#commit-messages)\r\n\r\n_See [the contribution guide](https://github.com/tektoncd/pipeline/blob/main/CONTRIBUTING.md)\r\nfor more details._\r\n\r\n# Release Notes\r\n\r\n<!--\r\nDoes your PR contain User facing changes?\r\n\r\nIf so, briefly describe them here so we can include this description in the\r\nrelease notes for the next release!\r\n-->\r\n\r\n```\r\nAdds GitHub status fetching and updates to Pull Request CRD.\r\n```\r\n",
   "Labels": [
     {
       "ID": 0,

config/config-feature-flags.yaml

@@ -27,7 +27,7 @@ data:
   # The default behaviour is for Tekton to create Affinity Assistants
   #
   # See more in the workspace documentation about Affinity Assistant
-  # https://github.com/tektoncd/pipeline/blob/master/docs/workspaces.md#affinity-assistant-and-specifying-workspace-order-in-a-pipeline
+  # https://github.com/tektoncd/pipeline/blob/main/docs/workspaces.md#affinity-assistant-and-specifying-workspace-order-in-a-pipeline
   # or https://github.com/tektoncd/pipeline/pull/2630 for more info.
   disable-affinity-assistant: "false"
   # Setting this flag to "true" will prevent Tekton overriding your

docs/README.md

@@ -54,8 +54,8 @@ Tekton Pipelines defines the following entities:
 
 ## Getting started
 
-To get started, complete the [Tekton Pipelines Tutorial](https://github.com/tektoncd/pipeline/blob/master/docs/tutorial.md) and go through our
-[examples](https://github.com/tektoncd/pipeline/tree/master/examples).
+To get started, complete the [Tekton Pipelines Tutorial](https://github.com/tektoncd/pipeline/blob/main/docs/tutorial.md) and go through our
+[examples](https://github.com/tektoncd/pipeline/tree/main/examples).
 
 ## Understanding Tekton Pipelines
 
@@ -76,7 +76,7 @@ See the following topics to learn how to use Tekton Pipelines in your project:
 
 ## Contributing to Tekton Pipelines
 
-If you'd like to contribute to the Tekton Pipelines project, see the [Tekton Pipeline Contributor's Guide](https://github.com/tektoncd/pipeline/blob/master/CONTRIBUTING.md).
+If you'd like to contribute to the Tekton Pipelines project, see the [Tekton Pipeline Contributor's Guide](https://github.com/tektoncd/pipeline/blob/main/CONTRIBUTING.md).
 
 ---
 

docs/conditions.md

@@ -93,7 +93,7 @@ The `description` field (optional) allows you to specify a meaningful descriptio
 
 ## Code examples
 
-For a better understanding of `Conditions`, study [our code examples](https://github.com/tektoncd/pipeline/tree/master/examples).
+For a better understanding of `Conditions`, study [our code examples](https://github.com/tektoncd/pipeline/tree/main/examples).
 
 ---
 

docs/deprecations.md

@@ -18,7 +18,7 @@ being deprecated.
 
 ## Deprecation Table
 
-| Feature Being Deprecated                                                                                                                      | Deprecation Announcement                                                     | [API Compatibility Policy](https://github.com/tektoncd/pipeline/tree/master/api_compatibility_policy.md) | Earliest Date or Release of Removal |
+| Feature Being Deprecated                                                                                                                      | Deprecation Announcement                                                     | [API Compatibility Policy](https://github.com/tektoncd/pipeline/tree/main/api_compatibility_policy.md) | Earliest Date or Release of Removal |
 | ------------------------                                                                                                                      | ------------------------                                                     | -------------------------------------------------------------------------------------------------------- | ------------------------            |
 | [`tekton.dev/task` label on ClusterTasks](https://github.com/tektoncd/pipeline/issues/2533)                                                   | [v0.12.0](https://github.com/tektoncd/pipeline/releases/tag/v0.12.0)         | Beta                                                                                                     | January 30 2021                     |
 | [Step `$HOME` env var defaults to `/tekton/home`](https://github.com/tektoncd/pipeline/issues/2013)                                           | [v0.11.0-rc1](https://github.com/tektoncd/pipeline/releases/tag/v0.11.0-rc1) | Beta                                                                                                     | December 4 2020                     |

docs/developers/local-setup.md

@@ -11,7 +11,7 @@ This section provides guidelines for running Tekton on your local workstation vi
 
 Complete these prerequisites to run Tekton locally using Docker Desktop:
 
-- Install the [required tools](https://github.com/tektoncd/pipeline/blob/master/DEVELOPMENT.md#requirements).
+- Install the [required tools](https://github.com/tektoncd/pipeline/blob/main/DEVELOPMENT.md#requirements).
 - Install [Docker Desktop](https://www.docker.com/products/docker-desktop) 
 - Configure Docker Desktop ([Mac](https://docs.docker.com/docker-for-mac/#resources), [Windows](https://docs.docker.com/docker-for-windows/#resources))to use six CPUs, 10 GB of RAM and 2GB of swap space.
 - Set `host.docker.internal:5000` as an insecure registry with Docker for Desktop. See the [Docker insecure registry documentation](https://docs.docker.com/registry/insecure/).
@@ -50,7 +50,7 @@ You must reconfigure any `image` resource definitions in your `PipelineResources
 
 Complete these prerequisites to run Tekton locally using Minikube:
 
-- Install the [required tools](https://github.com/tektoncd/pipeline/blob/master/DEVELOPMENT.md#requirements).
+- Install the [required tools](https://github.com/tektoncd/pipeline/blob/main/DEVELOPMENT.md#requirements).
 - Install [minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/) and start a session as follows:
 ```bash
 minikube start --memory 6144 --cpus 2

docs/install.md

@@ -30,7 +30,7 @@ This guide explains how to install Tekton Pipelines. It covers the following top
    * **[Nightly](../tekton/README.md#nightly-releases)** - may contain bugs,
      install at your own risk. Nightlies live at `gcr.io/tekton-nightly`.
    * **[`HEAD`]** - this is the bleeding edge. It contains unreleased code that may result
-     in unpredictable behavior. To get started, see the [development guide](https://github.com/tektoncd/pipeline/blob/master/DEVELOPMENT.md) instead of this page.
+     in unpredictable behavior. To get started, see the [development guide](https://github.com/tektoncd/pipeline/blob/main/DEVELOPMENT.md) instead of this page.
 
 1. Grant `cluster-admin` permissions to the current user.
 
@@ -279,7 +279,7 @@ The example below customizes the following:
 - the default service account from `default` to `tekton`.
 - the default timeout from 60 minutes to 20 minutes.
 - the default `app.kubernetes.io/managed-by` label is applied to all Pods created to execute `TaskRuns`.
-- the default Pod template to include a node selector to select the node where the Pod will be scheduled by default. A list of supported fields is available [here](https://github.com/tektoncd/pipeline/blob/master/docs/podtemplates.md#supported-fields).
+- the default Pod template to include a node selector to select the node where the Pod will be scheduled by default. A list of supported fields is available [here](https://github.com/tektoncd/pipeline/blob/main/docs/podtemplates.md#supported-fields).
   For more information, see [`PodTemplate` in `TaskRuns`](./taskruns.md#specifying-a-pod-template) or [`PodTemplate` in `PipelineRuns`](./pipelineruns.md#specifying-a-pod-template).
 - the default `Workspace` configuration can be set for any `Workspaces` that a Task declares but that a TaskRun does not explicitly provide
 
@@ -387,11 +387,11 @@ Out-of-the-box, Tekton Pipelines Controller is configured for relatively small-s
 
 ## Creating a custom release of Tekton Pipelines
 
-You can create a custom release of Tekton Pipelines by following and customizing the steps in [Creating an official release](https://github.com/tektoncd/pipeline/blob/master/tekton/README.md#create-an-official-release). For example, you might want to customize the container images built and used by Tekton Pipelines.
+You can create a custom release of Tekton Pipelines by following and customizing the steps in [Creating an official release](https://github.com/tektoncd/pipeline/blob/main/tekton/README.md#create-an-official-release). For example, you might want to customize the container images built and used by Tekton Pipelines.
 
 ## Next steps
 
-To get started with Tekton Pipelines, see the [Tekton Pipelines Tutorial](./tutorial.md) and take a look at our [examples](https://github.com/tektoncd/pipeline/tree/master/examples).
+To get started with Tekton Pipelines, see the [Tekton Pipelines Tutorial](./tutorial.md) and take a look at our [examples](https://github.com/tektoncd/pipeline/tree/main/examples).
 
 ---
 

docs/pipelines.md

@@ -1082,7 +1082,7 @@ In this example, `pipelineResults` in `status` will exclude the name-value pair
 can implement behavior that doesn't correspond directly to running a workload in a `Pod` on the cluster.
 For example, a custom task might execute some operation outside of the cluster and wait for its execution to complete.
 
-A PipelineRun starts a custom task by creating a [`Run`](https://github.com/tektoncd/pipeline/blob/master/docs/runs.md) instead of a `TaskRun`.
+A PipelineRun starts a custom task by creating a [`Run`](https://github.com/tektoncd/pipeline/blob/main/docs/runs.md) instead of a `TaskRun`.
 In order for a custom task to execute, there must be a custom task controller running on the cluster
 that is responsible for watching and updating `Run`s which reference their type. 
 If no such controller is running, those `Run`s will never complete and Pipelines using them will time out.
@@ -1175,7 +1175,7 @@ Pipelines do not support the following items with custom tasks:
 
 ## Code examples
 
-For a better understanding of `Pipelines`, study [our code examples](https://github.com/tektoncd/pipeline/tree/master/examples).
+For a better understanding of `Pipelines`, study [our code examples](https://github.com/tektoncd/pipeline/tree/main/examples).
 
 ---
 

docs/tasks.md

@@ -443,7 +443,7 @@ a `results` field but it's the responsibility of the `Task` to generate its cont
 It's important to note that Tekton does not perform any processing on the contents of results; they are emitted
 verbatim from your Task including any leading or trailing whitespace characters. Make sure to write only the
 precise string you want returned from your `Task` into the `/tekton/results/` files that your `Task` creates.
-You can use [`$(results.name.path)`](https://github.com/tektoncd/pipeline/blob/master/docs/variables.md#variables-available-in-a-task)
+You can use [`$(results.name.path)`](https://github.com/tektoncd/pipeline/blob/main/docs/variables.md#variables-available-in-a-task)
 to avoid having to hardcode this path.
 
 In the example below, the `Task` specifies two files in the `results` field:
@@ -738,7 +738,7 @@ Study the following code examples to better understand how to configure your `Ta
 - [Using a `Sidecar` in a `Task`](#using-a-sidecar-in-a-task)
 
 _Tip: See the collection of simple
-[examples](https://github.com/tektoncd/pipeline/tree/master/examples) for
+[examples](https://github.com/tektoncd/pipeline/tree/main/examples) for
 additional code samples._
 
 ### Building and pushing a Docker image

docs/tekton-controller-performance-configuration.md

@@ -22,7 +22,7 @@ This document will show us how to configure [tekton-pipeline-controller](./../co
 #### Configure Thread, QPS and Burst
 
 ---
-Default, the value of ThreadsPerController, QPS and Burst is [2](https://github.com/knative/pkg/blob/master/controller/controller.go#L58), [5.0](https://github.com/tektoncd/pipeline/blob/master/vendor/k8s.io/client-go/rest/config.go#L44) and [10](https://github.com/tektoncd/pipeline/blob/master/vendor/k8s.io/client-go/rest/config.go#L45) accordingly.
+Default, the value of ThreadsPerController, QPS and Burst is [2](https://github.com/knative/pkg/blob/master/controller/controller.go#L58), [5.0](https://github.com/tektoncd/pipeline/blob/main/vendor/k8s.io/client-go/rest/config.go#L44) and [10](https://github.com/tektoncd/pipeline/blob/main/vendor/k8s.io/client-go/rest/config.go#L45) accordingly.
 
 Sometimes, above default values can't meet performance requirements, then you need to overwrite these values. You can modify them in the [tekton controller deployment](./../config/controller.yaml). You can specify these customized values in the `tekton-pipelines-controller` container via `threads-per-controller`, `kube-api-qps` and `kube-api-burst` flags accordingly. For example:
 

docs/tutorial.md

@@ -17,7 +17,7 @@ specific to a given cloud computing service.
 
 ## Before you begin
 
-Before you begin this tutorial, make sure you have [installed and configured](https://github.com/tektoncd/pipeline/blob/master/docs/install.md)
+Before you begin this tutorial, make sure you have [installed and configured](https://github.com/tektoncd/pipeline/blob/main/docs/install.md)
 the latest release of Tekton on your Kubernetes cluster, including the
 [Tekton CLI](https://github.com/tektoncd/cli).