📖 Update links that were pointing to the master branch of amphtml…

… and associated repos (#33570)

.github/ISSUE_TEMPLATE/cherry_pick_template.md

@@ -12,7 +12,7 @@ assignees: ''
 MUST: Replace *everything* in angle brackets in the title AND body of this issue.
 MUST: Update issue labels to indicate which channels the cherry-pick is going into.
 
-If you have any questions see the [cherry-pick documentation](https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md#Cherry-picks).
+If you have any questions see the [cherry-pick documentation](https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md#Cherry-picks).
 -->
 
 # Cherry-pick request
@@ -25,7 +25,7 @@ TIP: Cherry-picks into Stable most likely require a cherry-pick into Beta / Expe
 | :---------------: | :------------: | :------------------: | :----------: | :----------: | ------------------------------------------------------------------------------- |
 | #<_ISSUE_NUMBER_> | #<_PR_NUMBER_> |     **<YES/NO>**     | **<YES/NO>** | **<YES/NO>** | #<_RELEASE_ISSUE_>                                                              |
 
-## Why does this issue meet the [cherry-pick criteria](https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md#Cherry-picks)?
+## Why does this issue meet the [cherry-pick criteria](https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md#Cherry-picks)?
 
 <!--
 TIP: Be specific.

.github/ISSUE_TEMPLATE/intent-to-deprecate--i2d-.md

@@ -10,7 +10,7 @@ assignees: ''
 <!--
 Replace/remove all of the text in brackets, including this text.
 
-See https://github.com/ampproject/amphtml/blob/master/spec/amp-versioning-policy.md for details on AMP's deprecation policy, instructions on filling out this I2D template and how to get help if you have questions.
+See https://github.com/ampproject/amphtml/blob/main/spec/amp-versioning-policy.md for details on AMP's deprecation policy, instructions on filling out this I2D template and how to get help if you have questions.
 
 If your feature can be removed immediately after deprecation, you can use this issue to track removal as well (changing the title to "Intent-to-Deprecate-and-Remove" and adding the "INTENT TO REMOVE" label).  Otherwise you will file a separate Intent-to-Remove (I2R) issue after the feature has been deprecated and you are ready to remove the feature.
 -->

.github/ISSUE_TEMPLATE/intent-to-implement--i2i-.md

@@ -1,6 +1,6 @@
 ---
 name: Intent-to-implement (I2I)
-about: Proposes a significant change/update to AMP. See https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md.
+about: Proposes a significant change/update to AMP. See https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md.
 title: 'I2I: <your feature/change>'
 labels: INTENT TO IMPLEMENT
 assignees: ''
@@ -10,9 +10,9 @@ assignees: ''
 <!--
 Replace/remove all of the text in brackets, including this text.
 
-See https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md for help determining if you need to file an I2I for your change/fix, instructions on filling out this I2I template and how to get help if you have questions. Note that If you are implementing a minor change/fix, you likely do not need to file this I2I.
+See https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md for help determining if you need to file an I2I for your change/fix, instructions on filling out this I2I template and how to get help if you have questions. Note that If you are implementing a minor change/fix, you likely do not need to file this I2I.
 
-If you haven't already done so, sign the Contributor License Agreement (CLA) as soon as possible to avoid delays merging your code. A signed CLA is not necessary to submit this I2I or to send a pull request, but it will be needed before your code can be merged. See https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md#contributor-license-agreement for more information on CLAs.
+If you haven't already done so, sign the Contributor License Agreement (CLA) as soon as possible to avoid delays merging your code. A signed CLA is not necessary to submit this I2I or to send a pull request, but it will be needed before your code can be merged. See https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md#contributor-license-agreement for more information on CLAs.
 -->
 
 ## Summary
@@ -49,7 +49,7 @@ You should add a link to the launch tracker for this work here if applicable. On
 -->
 
 <!--
-Add anyone to this cc line that you want to notify about this I2I, including a reviewer once you have found one. See https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md for help in finding a reviewer.
+Add anyone to this cc line that you want to notify about this I2I, including a reviewer once you have found one. See https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md for help in finding a reviewer.
 -->
 
 /cc @ampproject/wg-approvers

.github/ISSUE_TEMPLATE/intent-to-remove--i2r-.md

@@ -10,7 +10,7 @@ assignees: ''
 <!--
 Replace/remove all of the text in brackets, including this text.
 
-See https://github.com/ampproject/amphtml/blob/master/spec/amp-versioning-policy.md for details on AMP's deprecation policy, instructions on filling out this I2R template and how to get help if you have questions.
+See https://github.com/ampproject/amphtml/blob/main/spec/amp-versioning-policy.md for details on AMP's deprecation policy, instructions on filling out this I2R template and how to get help if you have questions.
 
 This I2R should be created after your Intent-to-Deprecate (I2D) for the feature was approved.
 -->

.github/ISSUE_TEMPLATE/intent-to-ship--i2s-.md

@@ -1,7 +1,7 @@
 ---
 name: Intent-to-ship (I2S)
 about: Proposes launching a significant change/update to AMP that has already been
-  implemented. https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md
+  implemented. https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md
 title: 'I2S: <your change/update>'
 labels: INTENT TO SHIP
 assignees: ''
@@ -12,7 +12,7 @@ assignees: ''
 Replace/remove all of the text in brackets, including this text.
 
 Use an Intent-to-ship (I2S) issue to request the launch of a significant change/update to AMP, generally those that required an Intent-to-implement (I2I) issue.
-See https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md for more information.
+See https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md for more information.
 -->
 
 ## Summary

.github/ISSUE_TEMPLATE/release-tracking-issue.md

@@ -52,7 +52,7 @@ If you perform cherry picks, add/update the checkboxes above as needed e.g.
 - [ ] Release <CHERRY_PICK_RELEASE_NUMBER> promoted to Experimental and Beta channels (<CL submit time>)
 -->
 
-See the [release documentation](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md) for more information on the release process, including how to test changes in the Experimental channel.
+See the [release documentation](https://github.com/ampproject/amphtml/blob/main/contributing/release-schedule.md) for more information on the release process, including how to test changes in the Experimental channel.
 
 If you find a bug in this build, please file an [issue](https://github.com/ampproject/amphtml/issues/new). If you believe the bug should be fixed in this build, follow the instructions in the [cherry picks documentation](https://go.amp.dev/cherry-picks).
 

.github/workflows/create-design-review-issue.js

@@ -61,13 +61,13 @@ const createBody = ({timeUtc, timeUrl, calendarUrl}) =>
 Time: [${timeUtc} UTC](${timeUrl}) ([add to Google Calendar](${calendarUrl}))
 Location: [Video conference via Google Meet](${vcUrl})
 
-The AMP community holds weekly engineering [design reviews](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md). **We encourage everyone in the community to participate in these design reviews.**
+The AMP community holds weekly engineering [design reviews](https://github.com/ampproject/amphtml/blob/main/contributing/design-reviews.md). **We encourage everyone in the community to participate in these design reviews.**
 
-If you are interested in bringing your design to design review, read the [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md) and add a link to your design doc or issue by the Monday before your design review.
+If you are interested in bringing your design to design review, read the [design review documentation](https://github.com/ampproject/amphtml/blob/main/contributing/design-reviews.md) and add a link to your design doc or issue by the Monday before your design review.
 
 When attending a design review please read through the designs _before_ the design review starts. This allows us to spend more time on discussion of the design.
 
-We rotate our design review between times that work better for different parts of the world as described in our [design review documentation](https://github.com/ampproject/amphtml/blob/master/contributing/design-reviews.md), but you are welcome to attend any design review. If you cannot make any of the design reviews but have a design to discuss please let mrjoro@ know on [Slack](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#discussion-channels) and we will find a time that works for you.
+We rotate our design review between times that work better for different parts of the world as described in our [design review documentation](https://github.com/ampproject/amphtml/blob/main/contributing/design-reviews.md), but you are welcome to attend any design review. If you cannot make any of the design reviews but have a design to discuss please let mrjoro@ know on [Slack](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#discussion-channels) and we will find a time that works for you.
 `.trim();
 
 function leadingZero(number) {

.lando.yml

@@ -1,6 +1,6 @@
 # This is a configuration file for a Lando-based local dev environment for amphtml.
 # It is an alternative to the existing local development environment to what is described in the Getting Started
-# End-to-end guide <https://github.com/ampproject/amphtml/blob/master/contributing/getting-started-e2e.md>.
+# End-to-end guide <https://github.com/ampproject/amphtml/blob/main/contributing/getting-started-e2e.md>.
 #
 # This environment allows you to encapsulate the amphtml development environment inside of a Docker container.
 # Instead of accessing <http://localhost:8000>, this environment can be accessed via <https://amphtml.lando.site>.

3p/README.md

@@ -17,7 +17,7 @@ Examples: Youtube, Vimeo videos; Tweets, Instagrams; comment systems; polls; qui
 -   Avoid client side rendering of iframe content.
 -   If your use of iframes is for style isolation, consider that AMP might provide an iframe-free alternative.
 -   If you can make it not-iframe-based that is much better. (See e.g. the pinterest embed). We will always ask to do this first. E.g. adding a CORS endpoint to your server might make this possible.
--   Must play well within [AMP's sizing framework](https://github.com/ampproject/amphtml/blob/master/spec/amp-html-layout.md).
+-   Must play well within [AMP's sizing framework](https://github.com/ampproject/amphtml/blob/main/spec/amp-html-layout.md).
 -   All JS on container page must be open source and bundled with AMP.
 -   JavaScript loaded into iframe should be reasonable with respect to functionality.
 -   Use the `sandbox` attribute on iframe if possible.
@@ -28,7 +28,7 @@ Examples: Youtube, Vimeo videos; Tweets, Instagrams; comment systems; polls; qui
 
 -   We welcome pull requests by all ad networks for inclusion into AMP.
 -   All ads and all sub resources must be served from HTTPS.
--   Must play well within [AMP's sizing framework](https://github.com/ampproject/amphtml/blob/master/spec/amp-html-layout.md).
+-   Must play well within [AMP's sizing framework](https://github.com/ampproject/amphtml/blob/main/spec/amp-html-layout.md).
 -   For display ads support, always implement amp-ad and instruct your client to use your amp-ad implementation instead of using amp-iframe. Althought amp-iframe will render the ad, ad clicks will break and viewability information is not available.
 -   Providing an optional image only zero-iframe embed is appreciated.
 -   Support viewability and other metrics/instrumentation as supplied by AMP (via postMessage API)
@@ -66,5 +66,5 @@ Review the [ads/README](../ads/README.md) for further details on ad integration.
 You should ensure there are integration tests for your extension. These should be added to the AMP
 repo where it makes sense. In some cases this won't be possible because it relies on bringing up
 third-party infrastructure. In these cases you should maintain testing for the extension on your
-infrastructure against both production AMP and [canary](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md#amp-experimental-and-beta-channels).
-Upon any monitored failures, an escalation can be raised in [regular AMP communication channel](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#discussion-channels).
+infrastructure against both production AMP and [canary](https://github.com/ampproject/amphtml/blob/main/contributing/release-schedule.md#amp-experimental-and-beta-channels).
+Upon any monitored failures, an escalation can be raised in [regular AMP communication channel](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#discussion-channels).

CODE_OF_CONDUCT.md

@@ -1 +1 @@
-See https://github.com/ampproject/meta/blob/master/CODE_OF_CONDUCT.md
+See https://github.com/ampproject/meta/blob/main/CODE_OF_CONDUCT.md

CONTRIBUTING.md

@@ -71,7 +71,7 @@ Technical issues, designs, etc. are discussed using several different channels:
 
 ### Working groups
 
-Most of the day-to-day work in building AMP happens in AMP's [Working Groups (WGs)](https://github.com/ampproject/meta/tree/master/working-groups). Getting involved in a WG is a great way to contribute to AMP.
+Most of the day-to-day work in building AMP happens in AMP's [Working Groups (WGs)](https://github.com/ampproject/meta/tree/main/working-groups). Getting involved in a WG is a great way to contribute to AMP.
 
 Most working groups post approximately bi-weekly [Status Update GitHub issues](https://github.com/search?q=org%3Aampproject+label%3A%22Type%3A+Status+Update%22&type=Issues).
 

GOVERNANCE.md

@@ -1 +1 @@
-See https://github.com/ampproject/meta/blob/master/GOVERNANCE.md
+See https://github.com/ampproject/meta/blob/main/GOVERNANCE.md

README.md

@@ -2,7 +2,7 @@
 
 ⚡⚡⚡
 
-[![Build Status](https://img.shields.io/circleci/build/github/ampproject/amphtml/master 'Build Status')](https://app.circleci.com/pipelines/github/ampproject/amphtml?branch=master)
+[![Build Status](https://img.shields.io/circleci/build/github/ampproject/amphtml/main 'Build Status')](https://app.circleci.com/pipelines/github/ampproject/amphtml?branch=main)
 [![GitHub Release](https://img.shields.io/github/release/ampproject/amphtml.svg?logo=GitHub&style=flat-square 'GitHub Release')](https://github.com/ampproject/amphtml/releases/latest)
 [![Commits](https://img.shields.io/github/commit-activity/m/ampproject/amphtml.svg?logo=GitHub&style=flat-square 'Commits')](https://github.com/ampproject/amphtml/pulse/monthly)
 [![Badges](https://img.shields.io/badge/badges-16-brightgreen?logo=GitHub&style=flat-square)](#)
@@ -51,19 +51,19 @@ AMP is an open source project, and we'd love your help making it better!
 
 -   The [amp.dev Support page](https://amp.dev/support/) has resources for getting help.
 -   Use [Stack Overflow](http://stackoverflow.com/questions/tagged/amp-html) to ask questions about using AMP and find answers to questions others have asked.
--   [Let us know about bugs](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#report-a-bug), and [file feature requests](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#make-a-suggestion) to suggest improvements.
+-   [Let us know about bugs](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#report-a-bug), and [file feature requests](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#make-a-suggestion) to suggest improvements.
 -   AMP accepts responsible security disclosures through the [Google Application Security program](https://www.google.com/about/appsecurity/).
 
 ## Want to help make AMP better?
 
--   [CONTRIBUTING.md](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md) has information on how you can help improve AMP, including [ongoing participation](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#ongoing-participation) through Slack, weekly design reviews, etc.
--   We strongly encourage [code contributions](https://github.com/ampproject/amphtml/blob/master/contributing/contributing-code.md)!
--   **We enthusiastically welcome new contributors to AMP _even if you have no experience being part of an open source project_**. We've made it easy to [get started contributing](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#get-started-with-open-source).
--   Consider joining one of AMP's [Working Groups](https://github.com/ampproject/meta/tree/master/working-groups), where most of the day-to-day work in AMP gets done.
+-   [CONTRIBUTING.md](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md) has information on how you can help improve AMP, including [ongoing participation](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#ongoing-participation) through Slack, weekly design reviews, etc.
+-   We strongly encourage [code contributions](https://github.com/ampproject/amphtml/blob/main/contributing/contributing-code.md)!
+-   **We enthusiastically welcome new contributors to AMP _even if you have no experience being part of an open source project_**. We've made it easy to [get started contributing](https://github.com/ampproject/amphtml/blob/main/CONTRIBUTING.md#get-started-with-open-source).
+-   Consider joining one of AMP's [Working Groups](https://github.com/ampproject/meta/tree/main/working-groups), where most of the day-to-day work in AMP gets done.
 
 ## Other useful information
 
--   [AMP's release documentation](contributing/release-schedule.md) provides details on how and when AMP releases new versions, including [how to know when a change is live in a release](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md#determining-if-your-change-is-in-a-release).
+-   [AMP's release documentation](contributing/release-schedule.md) provides details on how and when AMP releases new versions, including [how to know when a change is live in a release](https://github.com/ampproject/amphtml/blob/main/contributing/release-schedule.md#determining-if-your-change-is-in-a-release).
 -   [AMP's roadmap](https://amp.dev/community/roadmap) provides details on some of the significant projects we are working on.
--   The [AMP meta repository](https://github.com/ampproject/meta) has information _about_ the AMP open source project, including AMP's [governance](https://github.com/ampproject/meta/blob/master/GOVERNANCE.md).
--   [AMP's code of conduct](https://github.com/ampproject/meta/blob/master/CODE_OF_CONDUCT.md) documents how all members, committers and volunteers in the community are required to act. AMP strives for a positive and growing project community that provides a safe environment for everyone.
+-   The [AMP meta repository](https://github.com/ampproject/meta) has information _about_ the AMP open source project, including AMP's [governance](https://github.com/ampproject/meta/blob/main/GOVERNANCE.md).
+-   [AMP's code of conduct](https://github.com/ampproject/meta/blob/main/CODE_OF_CONDUCT.md) documents how all members, committers and volunteers in the community are required to act. AMP strives for a positive and growing project community that provides a safe environment for everyone.