[COIL] Change chromium code search type links to use main rather than master for content

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

Change-Id: I6b198276bc80ce4bfa772ef218e1c07b46e76c02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902344
Commit-Queue: John Palmer <jopalmer@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Auto-Submit: John Palmer <jopalmer@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#884359}

content/browser/buckets/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: "Blink>Storage>Buckets"

content/browser/loader/cross_origin_read_blocking_explainer.md

@@ -1,4 +1,4 @@
 # Cross-Origin Read Blocking (CORB)
 
 The Cross-Origin Read Blocking (CORB) explainer has been moved to
-[`//services/network/cross_origin_read_blocking.md`](https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md).
+[`//services/network/cross_origin_read_blocking.md`](https://chromium.googlesource.com/chromium/src/+/main/services/network/cross_origin_read_blocking_explainer.md).

content/browser/media/capture/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>Media>SurfaceCapture"

content/browser/sandbox_ipc_linux.h

@@ -2,7 +2,7 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-// https://chromium.googlesource.com/chromium/src/+/master/docs/linux/sandbox_ipc.md
+// https://chromium.googlesource.com/chromium/src/+/main/docs/linux/sandbox_ipc.md
 
 #ifndef CONTENT_BROWSER_SANDBOX_IPC_LINUX_H_
 #define CONTENT_BROWSER_SANDBOX_IPC_LINUX_H_

content/browser/service_worker/README.md

@@ -255,7 +255,7 @@ remotes to `mojom.blink.ServiceWorkerRegistrationObject` and
 > ServiceWorkerRegistration and ServiceWorker, or maybe prohibiting destructions
 > initiated from the renderer may work.
 > In addition, we have a Mojo interface for in-process communication across threads like
-> [this](https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/public/mojom/service_worker/controller_service_worker.mojom;l=95;drc=6e8b402a6231405b753919029c9027404325ea00).
+> [this](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/public/mojom/service_worker/controller_service_worker.mojom;l=95;drc=6e8b402a6231405b753919029c9027404325ea00).
 > Mojo is now slightly overused for abstraction of layers for service workers.
 
 #### Browser <-> Renderer (shared worker)
@@ -471,7 +471,7 @@ Here's the explanation about the each section:
 We run a limited number of
 [Telemetry](https://chromium.googlesource.com/catapult/+/HEAD/telemetry/README.md)
 benchmark tests for service worker and a few microbenchmarks in
-[blink_perf](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark/harnesses/blink_perf.md#service-worker-perf-tests)
+[blink_perf](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/benchmark/harnesses/blink_perf.md#service-worker-perf-tests)
 ([crbug](https://crbug.com/1019097)).
 
 Telemetry tests are part of the [Loading
@@ -513,7 +513,7 @@ Code links and resources:
 - PWA test suite: see 'pwa' in
   [loading_mobile.py](/tools/perf/page_sets/loading_mobile.py), as of March 2019
   [here](https://cs.chromium.org/chromium/src/tools/perf/page_sets/loading_mobile.py?l=88&rcl=e590d4e0ae6d3cbdabee199ea6fabe152a3eea83).
-- [cache_temperature.py](https://chromium.googlesource.com/catapult/+/master/telemetry/telemetry/page/cache_temperature.py)
+- [cache_temperature.py](https://chromium.googlesource.com/catapult/+/main/telemetry/telemetry/page/cache_temperature.py)
 - "Perf benchmark for PWAs using the loading benchmark": [crbug](https://crbug.com/736697) and
   [design doc](https://docs.google.com/document/d/1Nf97CVp1X7aSqvAspyJ7yOCDyr1osUNrnfrGwZ_Yuuo/edit?usp=sharing).
 

content/browser/sms/README.md

@@ -17,7 +17,7 @@ This is implemented in [third_party/blink/renderer/modules/credentialmanager](ht
 * The Android related tests are located in [chrome/android/javatests/src/org/chromium/chrome/browser/sms/](https://cs.chromium.org/chromium/src/chrome/android/javatests/src/org/chromium/chrome/browser/sms/).
 * Web platform tests are located in [third_party/blink/web_tests/http/tests/credentialmanager/](https://cs.chromium.org/chromium/src/third_party/blink/web_tests/http/tests/credentialmanager/)
 
-For how to run these tests, refer to Chromium documentation [Running tests locally](https://www.chromium.org/developers/testing/running-tests), [Android Test Instructions](https://chromium.googlesource.com/chromium/src/+/master/docs/testing/android_test_instructions.md)
+For how to run these tests, refer to Chromium documentation [Running tests locally](https://www.chromium.org/developers/testing/running-tests), [Android Test Instructions](https://chromium.googlesource.com/chromium/src/+/main/docs/testing/android_test_instructions.md)
 
 For testing this API locally, refer to [How to use the Web OTP API](https://github.com/WICG/WebOTP/blob/master/HOWTO.md)
 

content/browser/zygote_host/zygote_host_impl_linux.cc

@@ -116,7 +116,7 @@ void ZygoteHostImpl::Init(const base::CommandLine& command_line) {
   } else {
     LOG(FATAL)
         << "No usable sandbox! Update your kernel or see "
-           "https://chromium.googlesource.com/chromium/src/+/master/"
+           "https://chromium.googlesource.com/chromium/src/+/main/"
            "docs/linux/suid_sandbox_development.md for more information on "
            "developing with the SUID sandbox. "
            "If you want to live dangerously and need an immediate workaround, "

content/child/runtime_features.cc

@@ -429,7 +429,7 @@ void SetRuntimeFeaturesFromCommandLine(const base::CommandLine& command_line) {
   // SwitchToFeatureMap entry to the initializer list below.
   // Note: command line switches are now discouraged, please consider
   // using base::Feature instead.
-  // https://chromium.googlesource.com/chromium/src/+/refs/heads/master/docs/configuration.md#switches
+  // https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/configuration.md#switches
   using wrf = WebRuntimeFeatures;
   const SwitchToFeatureMap switchToFeatureMapping[] = {
       // Stable Features

content/common/zygote/zygote_communication_linux.h

@@ -28,7 +28,7 @@ namespace content {
 
 // Handles interprocess communication with the Linux zygote process. The zygote
 // does not use standard Chrome IPC or mojo, see:
-// https://chromium.googlesource.com/chromium/src/+/master/docs/linux/sandbox_ipc.md
+// https://chromium.googlesource.com/chromium/src/+/main/docs/linux/sandbox_ipc.md
 class CONTENT_EXPORT ZygoteCommunication {
  public:
   enum class ZygoteType { kSandboxed, kUnsandboxed };

content/public/browser/zygote_host/zygote_host_linux.h

@@ -12,7 +12,7 @@
 
 namespace content {
 
-// https://chromium.googlesource.com/chromium/src/+/master/docs/linux/zygote.md
+// https://chromium.googlesource.com/chromium/src/+/main/docs/linux/zygote.md
 
 // The zygote host is an interface, in the browser process, to the zygote
 // process.

content/public/common/content_descriptors.h

@@ -11,7 +11,7 @@
 // base::GlobalDescriptors object (see base/posix/global_descriptors.h)
 enum {
   kCrashDumpSignal,
-  kSandboxIPCChannel,  // https://chromium.googlesource.com/chromium/src/+/master/docs/linux/sandbox_ipc.md
+  kSandboxIPCChannel,  // https://chromium.googlesource.com/chromium/src/+/main/docs/linux/sandbox_ipc.md
   kMojoIPCChannel,
   kFieldTrialDescriptor,
 

content/public/test/README.md

@@ -58,7 +58,7 @@ execution:
 
 A wide range of methods are provided to simulate input such as clicks, touch,
 mouse moves and so on. Many reside in
-https://source.chromium.org/chromium/chromium/src/+/master:content/public/test/browser_test_utils.h.
+https://source.chromium.org/chromium/chromium/src/+/main:content/public/test/browser_test_utils.h.
 
 When using input in tests, be aware that the renderer drops all input
 received when the main frame is not being updated or rendered immediately
@@ -208,5 +208,5 @@ The embedded test server also registers [other default
 handlers][test-server-default-handlers] that may be useful.
 
 [host-resolver-config]: README.md#Cross_origin-navigations
-[cross-site-iframe-factory]: https://source.chromium.org/chromium/chromium/src/+/master:content/test/data/cross_site_iframe_factory.html
-[test-server-default-handlers]: https://source.chromium.org/chromium/chromium/src/+/master:net/test/embedded_test_server/default_handlers.cc
+[cross-site-iframe-factory]: https://source.chromium.org/chromium/chromium/src/+/main:content/test/data/cross_site_iframe_factory.html
+[test-server-default-handlers]: https://source.chromium.org/chromium/chromium/src/+/main:net/test/embedded_test_server/default_handlers.cc

content/renderer/content_security_policy_util_fuzzer.cc

@@ -10,7 +10,7 @@
 // # ./out/libfuzzer/content_security_policy_util_fuzzer
 //
 // For more details, see
-// https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/README.md
+// https://chromium.googlesource.com/chromium/src/+/main/testing/libfuzzer/README.md
 
 #include "base/at_exit.h"
 #include "base/command_line.h"

content/renderer/renderer_main_platform_delegate_linux.cc

@@ -31,7 +31,7 @@ void RendererMainPlatformDelegate::PlatformUninitialize() {
 
 bool RendererMainPlatformDelegate::EnableSandbox() {
   // The setuid sandbox is started in the zygote process: zygote_main_linux.cc
-  // https://chromium.googlesource.com/chromium/src/+/master/docs/linux/suid_sandbox.md
+  // https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox.md
   //
   // Anything else is started in InitializeSandbox().
   sandbox::policy::SandboxLinux::Options options;

content/test/gpu/gather_power_measurement_results.py

@@ -105,7 +105,7 @@ def GetJsonForLatestNBuilds(bot, build_count):
 
 def FindStepLogURL(steps, step_name, log_name):
   # The format of this JSON-encoded protobuf is defined here:
-  # https://chromium.googlesource.com/infra/luci/luci-go/+/master/
+  # https://chromium.googlesource.com/infra/luci/luci-go/+/main/
   #   buildbucket/proto/step.proto
   # It's easiest to just use the RPC explorer to fetch one and see
   # what's desired to extract.

content/test/gpu/gather_swarming_json_results.py

@@ -95,7 +95,7 @@ def JsonLoadFromUrl(url):
 
 def FindStepLogURL(steps, step_name, log_name):
   # The format of this JSON-encoded protobuf is defined here:
-  # https://chromium.googlesource.com/infra/luci/luci-go/+/master/
+  # https://chromium.googlesource.com/infra/luci/luci-go/+/main/
   #   buildbucket/proto/step.proto
   # It's easiest to just use the RPC explorer to fetch one and see
   # what's desired to extract.

content/test/gpu/trim_culprit_cls.py

@@ -44,7 +44,7 @@ import subprocess
 # Schemas:
 # - go/buildbucket-bq and go/buildbucket-proto/build.proto
 # - go/luci/cq/bq and
-#   https://source.chromium.org/chromium/infra/infra/+/master:go/src/go.chromium.org/luci/cv/api/bigquery/v1/attempt.proto
+#   https://source.chromium.org/chromium/infra/infra/+/main:go/src/go.chromium.org/luci/cv/api/bigquery/v1/attempt.proto
 #
 # Original author: maruel@
 # pylint: enable=line-too-long

content/zygote/zygote_linux.cc

@@ -48,7 +48,7 @@
 #include "third_party/icu/source/i18n/unicode/timezone.h"
 
 // See
-// https://chromium.googlesource.com/chromium/src/+/master/docs/linux/zygote.md
+// https://chromium.googlesource.com/chromium/src/+/main/docs/linux/zygote.md
 
 namespace content {
 
@@ -100,7 +100,7 @@ bool Zygote::ProcessRequests() {
   // browser on it.
   // A SOCK_DGRAM is installed in fd 5. This is the sandbox IPC channel.
   // See
-  // https://chromium.googlesource.com/chromium/src/+/master/docs/linux/sandbox_ipc.md
+  // https://chromium.googlesource.com/chromium/src/+/main/docs/linux/sandbox_ipc.md
 
   // We need to accept SIGCHLD, even though our handler is a no-op because
   // otherwise we cannot wait on children. (According to POSIX 2001.)

content/zygote/zygote_linux.h

@@ -142,7 +142,7 @@ class Zygote {
   std::vector<ZygoteProcessInfo> to_reap_;
 
   // Sandbox IPC channel for renderers to invoke services from the browser. See
-  // https://chromium.googlesource.com/chromium/src/+/master/docs/linux/sandbox_ipc.md
+  // https://chromium.googlesource.com/chromium/src/+/main/docs/linux/sandbox_ipc.md
   base::GlobalDescriptors::Descriptor ipc_backchannel_;
 };
 

content/zygote/zygote_main_linux.cc

@@ -108,7 +108,7 @@ static bool EnterSuidSandbox(sandbox::SetuidSandboxClient* setuid_sandbox,
   if (!setuid_sandbox->IsSuidSandboxUpToDate()) {
     LOG(WARNING) << "You are using a wrong version of the setuid binary!\n"
                     "Please read "
-                    "https://chromium.googlesource.com/chromium/src/+/master/"
+                    "https://chromium.googlesource.com/chromium/src/+/main/"
                     "docs/linux/suid_sandbox_development.md."
                     "\n\n";
   }