[COIL] Change chromium code search type links to use main rather than…

… master for docs

    See this doc: go/chromium-coil-change for more info
    BUG=1210385

Change-Id: I6cd8548301e360bae8e71384dbd8ef11aa6c985f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902904
Reviewed-by: My Nguyen <[email protected]>
Commit-Queue: My Nguyen <[email protected]>
Auto-Submit: John Palmer <[email protected]>
Cr-Commit-Position: refs/heads/master@{#885851}

docs/DIR_METADATA

@@ -1,10 +1,10 @@
 # Metadata information for this directory.
 #
 # For more information on DIR_METADATA files, see:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
 #
 # For the schema of this file, see Metadata message:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
 
 # build@ isn't really the right component for this, but it'll
 # do until we create a component for documentation.

docs/README.md

@@ -4,7 +4,7 @@ This directory contains chromium project documentation in
 [Gitiles-flavored Markdown].  It is automatically [rendered by Gitiles].
 
 [Gitiles-flavored Markdown]: https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md
-[rendered by Gitiles]: https://chromium.googlesource.com/chromium/src/+/master/docs/
+[rendered by Gitiles]: https://chromium.googlesource.com/chromium/src/+/main/docs/
 
 If you add new documents, please also add a link to them in the Document Index
 below.

docs/accessibility/DIR_METADATA

@@ -1,10 +1,10 @@
 # Metadata information for this directory.
 #
 # For more information on DIR_METADATA files, see:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
 #
 # For the schema of this file, see Metadata message:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
 
 monorail {
   component: "Internals>Accessibility"

docs/accessibility/espeak.md

@@ -92,7 +92,7 @@ The next steps require that you have the full Chrome OS source code
 checked out and you're in your chroot. See the Chromium OS Developer Guide
 for instructions:
 
-https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md
+https://chromium.googlesource.com/chromiumos/docs/+/main/developer_guide.md
 
 
 espeak-ng is in this directory:

docs/accessibility/ia2_to_uia.md

@@ -131,7 +131,7 @@ does not require the shared unique id. Consider the same example above.
 ~~~
 
 ## Docs & References:
-[Custom UIA Property and Pattern registration in Chromium](https://chromium.googlesource.com/chromium/src/+/master/ui/accessibility/platform/uia_registrar_win.h)
+[Custom UIA Property and Pattern registration in Chromium](https://chromium.googlesource.com/chromium/src/+/main/ui/accessibility/platform/uia_registrar_win.h)
 
 [UI Automation IItemContainerPattern. It is used to look up IAccessible2 element
 via a unique id](https://docs.microsoft.com/en-us/windows/win32/api/uiautomationclient/nn-uiautomationclient-iuiautomationitemcontainerpattern)

docs/accessibility/overview.md

@@ -510,9 +510,9 @@ which is renderer-side code, and in JavaScript by the [automation API]. The API
 is defined by [automation.idl], which must be kept synchronized with
 [ax_enums.mojom].
 
-[ax.mojom.AXActionData]: https://source.chromium.org/chromium/chromium/src/+/master:ui/accessibility/mojom/ax_action_data.mojom;l=13
-[ax.mojom.RenderAccessibilityHost::HandleAXEvents()]: https://source.chromium.org/chromium/chromium/src/+/master:content/common/render_accessibility.mojom;l=47
-[ax.mojom.RenderAccessibility.PerformAction()]: https://source.chromium.org/chromium/chromium/src/+/master:content/common/render_accessibility.mojom;l=86
+[ax.mojom.AXActionData]: https://source.chromium.org/chromium/chromium/src/+/main:ui/accessibility/mojom/ax_action_data.mojom;l=13
+[ax.mojom.RenderAccessibilityHost::HandleAXEvents()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=47
+[ax.mojom.RenderAccessibility.PerformAction()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=86
 [AutomationInternalCustomBindings]: https://cs.chromium.org/chromium/src/extensions/renderer/api/automation/automation_internal_custom_bindings.h
 [AXContentNodeData]: https://cs.chromium.org/chromium/src/content/common/ax_content_node_data.h
 [AXLayoutObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_layout_object.h
@@ -530,7 +530,7 @@ is defined by [automation.idl], which must be kept synchronized with
 [ViewAccessibility]: https://cs.chromium.org/chromium/src/ui/views/accessibility/view_accessibility.h
 [Node]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/dom/node.h
 [RenderAccessibilityImpl]: https://cs.chromium.org/chromium/src/content/renderer/accessibility/render_accessibility_impl.h
-[RenderAccessibilityManager]: https://source.chromium.org/chromium/chromium/src/+/master:content/renderer/accessibility/render_accessibility_manager.h
+[RenderAccessibilityManager]: https://source.chromium.org/chromium/chromium/src/+/main:content/renderer/accessibility/render_accessibility_manager.h
 [RenderFrameHostImpl]: https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_frame_host_impl.h
 [ui::AXNodeData]: https://cs.chromium.org/chromium/src/ui/accessibility/ax_node_data.h
 [WebAXObject]: https://cs.chromium.org/chromium/src/third_party/blink/public/web/web_ax_object.h

docs/accessibility/reader_mode.md

@@ -11,7 +11,7 @@ project is integrated into Chrome on Desktop.
 ## Overview
 
 Desktop Reader Mode is hidden behind a
-[base::Feature](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/core/dom_distiller_features.cc)
+[base::Feature](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/core/dom_distiller_features.cc)
 flag, ‘enable-reader-mode’. To run Chrome with Reader Mode, set the “Enable
 Reader Mode” flag to “Enabled” in chrome://flags or start Chrome with
 --enable-feature=”ReaderMode”.
@@ -72,7 +72,7 @@ forwards it to all registered observers, and caches it.
 ### Toggling Reader Mode
 Users can toggle reader mode using an omnibox icon or an option, Toggle Reader
 Mode, in the “customize and control Chrome” menu, both of which execute
-BrowserCommands [ToggleDistilledView()](https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/browser_commands.cc;bpv=1;bpt=1;l=1364?q=browser_commands%20dom_distiller&ss=chromium%2Fchromium%2Fsrc).
+BrowserCommands [ToggleDistilledView()](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/browser_commands.cc;bpv=1;bpt=1;l=1364?q=browser_commands%20dom_distiller&ss=chromium%2Fchromium%2Fsrc).
 
 [ReaderModeIconView](https://cs.chromium.org/chromium/src/chrome/browser/ui/views/reader_mode/reader_mode_icon_view.h)
 is a DistillabilityObserver and sets its visibility based on the latest result
@@ -144,7 +144,7 @@ considered a black box.
 
 In short, content is extracted from the fully rendered article via Javascript
 (specifically from the compiled Javascript file built from DOM Distiller,
-[domdistiller.js](https://source.chromium.org/chromium/chromium/src/+/master:third_party/dom_distiller_js/dist/js/domdistiller.js))
+[domdistiller.js](https://source.chromium.org/chromium/chromium/src/+/main:third_party/dom_distiller_js/dist/js/domdistiller.js))
 into a DistilledPageProto.
 
 The DOM Distiller retrieves the currently loaded document’s DOM and converts it
@@ -166,11 +166,11 @@ the following:
 
 ### Displaying Reader Mode Pages
 
-A [DistilledPageProto](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/core/proto/distilled_page.proto)
+A [DistilledPageProto](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/core/proto/distilled_page.proto)
 is created for each page distilled, and is used to generate the HTML of the
 distilled page.
 
 Pages are loaded by
-[DomDistillerViewerSource](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/content/browser/dom_distiller_viewer_source.h),
+[DomDistillerViewerSource](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/content/browser/dom_distiller_viewer_source.h),
 which serves the HTML and resources for viewing pages. After the DOM is
 initially loaded, the contents are populated via Javascript.

docs/accessibility/tests.md

@@ -44,7 +44,7 @@ out/release/content_shell \
 ```
 
 For information on modifying or adding web tests, see the main
-[web tests documentation](https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_tests.md).
+[web tests documentation](https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_tests.md).
 
 ## DumpAccessibilityTree tests
 

docs/ad_tagging.md

@@ -9,7 +9,7 @@ behavior](https://support.google.com/webtools/answer/7347327).
 
 The ad detection infrastructure is called Ad Tagging. Ad Tagging works by
 matching resource requests against a filter list (see how the list is
-[generated](https://chromium.googlesource.com/chromium/src.git/+/master/components/subresource_filter/FILTER_LIST_GENERATION.md))
+[generated](https://chromium.googlesource.com/chromium/src.git/+/main/components/subresource_filter/FILTER_LIST_GENERATION.md))
 to determine if they’re ad requests. Any requests matching the filter are tagged
 as ads. Further, requests (and some DOM elements such as iframes) made on behalf
 of previously tagged scripts are also tagged as ads by the
@@ -23,7 +23,7 @@ request made within an ad iframe is considered an ad resource request.
 
 ### Subresource Filter
 The [Subresource
-Filter](https://chromium.googlesource.com/chromium/src.git/+/master/components/subresource_filter/README.md)
+Filter](https://chromium.googlesource.com/chromium/src.git/+/main/components/subresource_filter/README.md)
 loads the filter list and matches urls against it. The list is distributed via
 the component updater. This same list and component is used for blocking ads on
 abusive sites and those that violate the Better Ads Standard.

docs/android_build_instructions.md

@@ -400,7 +400,7 @@ will not fail if an analysis check fails. Make sure to check the terminal that
 the server is running in at regular intervals to fix outstanding issues caught
 by these analysis checks.
 
-[fast_local_dev]: https://source.chromium.org/chromium/chromium/src/+/master:build/android/fast_local_dev_server.py
+[fast_local_dev]: https://source.chromium.org/chromium/chromium/src/+/main:build/android/fast_local_dev_server.py
 
 #### Incremental Install
 [Incremental Install](/build/android/incremental_install/README.md) uses

docs/android_debugging_instructions.md

@@ -20,7 +20,7 @@ out/Default/bin/chrome_public_apk launch --args='--disable-fre' 'data:text/html;
 ```
 
 ## Logging
-[Chromium logging from LOG(INFO)](https://chromium.googlesource.com/chromium/src/+/master/docs/android_logging.md)
+[Chromium logging from LOG(INFO)](https://chromium.googlesource.com/chromium/src/+/main/docs/android_logging.md)
 etc., is directed to the Android logcat logging facility. You can filter the
 messages, e.g. view chromium verbose logging, everything else at warning level
 with:

docs/autofill/DIR_METADATA

@@ -1,10 +1,10 @@
 # Metadata information for this directory.
 #
 # For more information on DIR_METADATA files, see:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
 #
 # For the schema of this file, see Metadata message:
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
 
 monorail {
   component: "UI>Browser>Autofill"

docs/chrome_os_logging.md

@@ -39,5 +39,5 @@ When actively debugging issues, Chrome's `--vmodule` flag is sometimes used to
 temporarily log messages at lower severities for particular modules.
 
 [base/logging.h]: ../base/logging.h
-[session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/master/login_manager/
-[Passing Chrome flags from session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/master/login_manager/docs/flags.md
+[session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/main/login_manager/
+[Passing Chrome flags from session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/main/login_manager/docs/flags.md

docs/chrome_untrusted.md

@@ -57,7 +57,7 @@ Yes, but not by default and with some caveats.
 
 Any team that requires extra capabilities granted to `chrome-untrusted://` should consult with the security team to ensure they are non-dangerous. In this context, we consider non-dangerous any API that we would expose to the renderer process, e.g. UMA.
 
-We currently use `postMessage()` to expose certain APIs to `chrome-untrusted://`. For example, the Media App uses `postMessage()` to pass a read-only file handle to `chrome-untrusted://media-app` from `chrome-untrusted://`. Teams are encouraged to get a review from someone in [SECURITY_OWNERS](https://source.chromium.org/chromium/chromium/src/+/master:ipc/SECURITY_OWNERS) when exposing capabilities over postMessage.
+We currently use `postMessage()` to expose certain APIs to `chrome-untrusted://`. For example, the Media App uses `postMessage()` to pass a read-only file handle to `chrome-untrusted://media-app` from `chrome-untrusted://`. Teams are encouraged to get a review from someone in [SECURITY_OWNERS](https://source.chromium.org/chromium/chromium/src/+/main:ipc/SECURITY_OWNERS) when exposing capabilities over postMessage.
 
 We are hoping to move to Mojo to improve auditability of these APIs and to make the security review required.
 
@@ -118,7 +118,7 @@ class UntrustedExampleUI : public ui::UntrustedWebUIController {
 
 2. Register the WebUIConfig
 
-Add the `WebUIConfig` to the list of WebUIConfigs in `[ChromeUntrustedWebUIControllerFactory](https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/webui/chrome_untrusted_web_ui_controller_factory.cc)`.
+Add the `WebUIConfig` to the list of WebUIConfigs in `[ChromeUntrustedWebUIControllerFactory](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/webui/chrome_untrusted_web_ui_controller_factory.cc)`.
 
 ```cpp
 register_config(std::make_unique<chromeos::UntrustedExampleUIConfig>());

docs/chromeos_build_instructions.md

@@ -18,7 +18,7 @@ build configurations:
 ## Common setup
 
 First, follow the [normal Linux build
-instructions](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md)
+instructions](https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md)
 as usual to get a Chromium checkout.
 
 You'll also need to add `'chromeos'` to the `target_os` list in your `.gclient`
@@ -98,8 +98,8 @@ Some useful flags:
      virtual screens, by display position and size.
 *    `--enable-features=Feature1,OtherFeature2`: Enable specified features.
      Features are often listed in chrome://flags, or in source files such as
-     [chrome_features.cc](https://source.chromium.org/chromium/chromium/src/+/master:chrome/common/chrome_features.cc)
-     or [ash_features.cc](https://source.chromium.org/chromium/chromium/src/+/master:ash/constants/ash_features.cc).
+     [chrome_features.cc](https://source.chromium.org/chromium/chromium/src/+/main:chrome/common/chrome_features.cc)
+     or [ash_features.cc](https://source.chromium.org/chromium/chromium/src/+/main:ash/constants/ash_features.cc).
      Note that changing values in chrome://flags does not work for
      linux-chromeos, and this flag must be used.
 *    `--enable-ui-devtools[=9223]`: Allow debugging of the system UI through
@@ -201,4 +201,4 @@ supplied in the imported .gni file after the `import()` line.
 
 For more information (like copying the locally-built Chrome to a device, or
 running Tast tests), consult Simple Chrome's
-[full documentation](https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md).
+[full documentation](https://chromium.googlesource.com/chromiumos/docs/+/main/simple_chrome_workflow.md).

docs/chromeos_glossary.md

@@ -1 +1 @@
-See [Chromium OS Glossary](https://chromium.googlesource.com/chromiumos/docs/+/master/glossary.md)
+See [Chromium OS Glossary](https://chromium.googlesource.com/chromiumos/docs/+/main/glossary.md)

docs/cipd_and_3pp.md

@@ -11,7 +11,7 @@
   specified in [DEPS] and updated via `gclient sync`.
 * You can [browse Chromium's CIPD repository][browse] online.
 
-[CIPD]: https://chromium.googlesource.com/infra/luci/luci-go/+/master/cipd/README.md
+[CIPD]: https://chromium.googlesource.com/infra/luci/luci-go/+/main/cipd/README.md
 [DEPS]: /DEPS
 [browse]: https://chrome-infra-packages.appspot.com/p/chromium
 
@@ -23,7 +23,7 @@
 * By specifying a 3pp package, you can define how to build certain artifacts and
   where to upload to CIPD. Then our packagers will do the rest for you.
 
-[support_3pp]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#recipe_modules-support_3pp
+[support_3pp]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#recipe_modules-support_3pp
 
 ## Why use CIPD & 3pp?:
 
@@ -96,9 +96,9 @@ into two main sections:
 * `upload`: contains some details on how the final result gets uploaded to CIPD.
    See [here][doc_upload] for more details.
 
-[`spec.proto`]: https://chromium.googlesource.com/infra/infra/+/master/recipes/recipe_modules/support_3pp/spec.proto
-[doc_create]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#creation-stages
-[doc_upload]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#upload
+[`spec.proto`]: https://chromium.googlesource.com/infra/infra/+/main/recipes/recipe_modules/support_3pp/spec.proto
+[doc_create]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#creation-stages
+[doc_upload]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#upload
 
 Staying with the example from above, the file `sample_cipd_dep/3pp/3pp.pb` may
 be like the following:
@@ -355,7 +355,7 @@ cipd_package_definition("my_cipd_package") {
   sources = [ "//path/to:test_binary_file" ]
 }
 ```
-[build/cipd/cipd.gni]: https://source.chromium.org/chromium/chromium/src/+/master:build/cipd/cipd.gni
+[build/cipd/cipd.gni]: https://source.chromium.org/chromium/chromium/src/+/main:build/cipd/cipd.gni
 
 ### Permissions in CIPD
 

docs/clang_sheriffing.md

@@ -198,7 +198,7 @@ work on linker bugs without having to have a Chromium build environment.
 To use `ld.lld`'s `--reproduce` flag, follow these steps:
 
 1. Locally (build Chromium with a locally-built
-   clang)[https://chromium.googlesource.com/chromium/src.git/+/master/docs/clang.md#Using-a-custom-clang-binary]
+   clang)[https://chromium.googlesource.com/chromium/src.git/+/main/docs/clang.md#Using-a-custom-clang-binary]
 
 1. After reproducing the link error, build just the failing target with
    ninja's `-v -d keeprsp` flags added: