diff --git a/README.md b/README.md index 6f6211cbb..4c8b8696a 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ Alan Cleaver is licensed under CC BY 2.0 [![GoDoc](https://godoc.org/github.com/knative/pkg?status.svg)](https://godoc.org/github.com/knative/pkg) [![Go Report Card](https://goreportcard.com/badge/knative/pkg)](https://goreportcard.com/report/knative/pkg) -[![codecov](https://codecov.io/gh/knative/pkg/branch/master/graph/badge.svg)](https://codecov.io/gh/knative/pkg) +[![codecov](https://codecov.io/gh/knative/pkg/branch/main/graph/badge.svg)](https://codecov.io/gh/knative/pkg) Knative `pkg` provides a place for sharing common Knative packages across the Knative repos. diff --git a/apis/duck/ABOUT.md b/apis/duck/ABOUT.md index 98ffc9424..b223412a0 100644 --- a/apis/duck/ABOUT.md +++ b/apis/duck/ABOUT.md @@ -73,7 +73,7 @@ the resulting JSON Patch can only contain fields relevant to the resource. In Knative, we follow the Kubernetes API principles of using `conditions` as a key part of our resources’ status, but we go a step further in -[defining particular conventions](https://github.com/knative/serving/blob/master/docs/spec/errors.md#error-conditions-and-reporting) +[defining particular conventions](https://github.com/knative/serving/blob/main/docs/spec/errors.md#error-conditions-and-reporting) on how these are used. To support this, we define: diff --git a/metrics/config.go b/metrics/config.go index c4c9c7f84..6407a1b0d 100644 --- a/metrics/config.go +++ b/metrics/config.go @@ -41,7 +41,7 @@ const ( DomainEnv = "METRICS_DOMAIN" // The following keys are used to configure metrics reporting. - // See https://github.com/knative/serving/blob/master/config/config-observability.yaml + // See https://github.com/knative/serving/blob/main/config/config-observability.yaml // for details. allowStackdriverCustomMetricsKey = "metrics.allow-stackdriver-custom-metrics" collectorAddressKey = "metrics.opencensus-address" diff --git a/metrics/exporter.go b/metrics/exporter.go index 3fc4966fd..46e5916de 100644 --- a/metrics/exporter.go +++ b/metrics/exporter.go @@ -81,7 +81,7 @@ type ExporterOptions struct { PrometheusHost string // ConfigMap is the data from config map config-observability. Must be present. - // See https://github.com/knative/serving/blob/master/config/config-observability.yaml + // See https://github.com/knative/serving/blob/main/config/config-observability.yaml // for details. ConfigMap map[string]string diff --git a/test/README.md b/test/README.md index d106ffec9..c56070878 100644 --- a/test/README.md +++ b/test/README.md @@ -28,7 +28,7 @@ You can use the test library in this dir to: These flags are useful for running against an existing cluster, making use of your existing -[environment setup](https://github.com/knative/serving/blob/master/DEVELOPMENT.md#environment-setup). +[environment setup](https://github.com/knative/serving/blob/main/DEVELOPMENT.md#environment-setup). By importing `knative.dev/pkg/test` you get access to a global variable called `test.Flags` which holds the values of @@ -46,7 +46,7 @@ _See [e2e_flags.go](./e2e_flags.go)._ debug logs will be emitted to stdout. We are using a generic -[FormatLogger](https://github.com/knative/pkg/blob/master/test/logging/logging.go#L49) +[FormatLogger](https://github.com/knative/pkg/blob/main/test/logging/logging.go#L49) that can be passed in any existing logger that satisfies it. Test can use the generic [logging methods](https://golang.org/pkg/testing/#T) to log info and error logs. All the common methods accept generic FormatLogger as a parameter @@ -64,7 +64,7 @@ _See [logging.go](./logging/logging.go)._ ### Check Knative Serving resources _WARNING: this code also exists in -[`knative/serving`](https://github.com/knative/serving/blob/master/test/adding_tests.md#make-requests-against-deployed-services)._ +[`knative/serving`](https://github.com/knative/serving/blob/main/test/adding_tests.md#make-requests-against-deployed-services)._ After creating Knative Serving resources or making changes to them, you will need to wait for the system to realize those changes. You can use the Knative diff --git a/test/logstream/README.md b/test/logstream/README.md index 18577b855..7c7886bd5 100644 --- a/test/logstream/README.md +++ b/test/logstream/README.md @@ -8,7 +8,7 @@ This is a guide to start using `logstream` in your e2e testing. knative test scripts already define this, and in some places (e.g. serving) randomize it. However, to facilitate usage outside of CI, you should consider including a package like - [this](https://github.com/knative/serving/blob/master/test/defaultsystem/system.go) + [this](https://github.com/knative/serving/blob/main/test/defaultsystem/system.go) and linking it like [this](https://github.com/knative/serving/blob/e797247322b5aa35001152d2a2715dbc20a86cc4/test/conformance.go#L20-L23) @@ -49,4 +49,4 @@ Now, any log statements that the library prints through this logger will appear in the logstream! For an example of this pattern, see -[the knative/networking prober library](https://github.com/knative/networking/blob/master/pkg/status/status.go). +[the knative/networking prober library](https://github.com/knative/networking/blob/main/pkg/status/status.go). diff --git a/test/mako/sidecar.go b/test/mako/sidecar.go index ff890f624..2b6057c1e 100644 --- a/test/mako/sidecar.go +++ b/test/mako/sidecar.go @@ -53,7 +53,7 @@ const ( // These token settings are for alerter. // If we want to enable the alerter for a benchmark, we need to mount the // token to the pod, with the same name and path. - // See https://github.com/knative/serving/blob/master/test/performance/benchmarks/dataplane-probe/continuous/dataplane-probe.yaml + // See https://github.com/knative/serving/blob/main/test/performance/benchmarks/dataplane-probe/continuous/dataplane-probe.yaml tokenFolder = "/var/secret" githubToken = "github-token" slackReadToken = "slack-read-token" diff --git a/test/zipkin/util.go b/test/zipkin/util.go index 95659c3b4..5e9cb5feb 100644 --- a/test/zipkin/util.go +++ b/test/zipkin/util.go @@ -46,7 +46,7 @@ const ( ZipkinTraceIDHeader = "ZIPKIN_TRACE_ID" // ZipkinPort is port exposed by the Zipkin Pod - // https://github.com/knative/serving/blob/master/config/monitoring/200-common/100-zipkin.yaml#L25 configures the Zipkin Port on the cluster. + // https://github.com/knative/serving/blob/main/config/monitoring/200-common/100-zipkin.yaml#L25 configures the Zipkin Port on the cluster. ZipkinPort = 9411 // ZipkinTraceEndpoint port-forwarded zipkin endpoint diff --git a/version/version.go b/version/version.go index 34504debf..b2a4e2b47 100644 --- a/version/version.go +++ b/version/version.go @@ -32,7 +32,7 @@ const ( // NOTE: If you are changing this line, please also update the minimum kubernetes // version listed here: - // https://github.com/knative/docs/blob/master/docs/install/any-kubernetes-cluster.md#before-you-begin + // https://github.com/knative/docs/blob/main/docs/install/any-kubernetes-cluster.md#before-you-begin defaultMinimumVersion = "v1.17.0" ) diff --git a/webhook/psbinding/README.md b/webhook/psbinding/README.md index e73ccf858..4715a3e67 100644 --- a/webhook/psbinding/README.md +++ b/webhook/psbinding/README.md @@ -3,7 +3,7 @@ The `psbinding` package provides facilities to make authoring [Bindings](https://docs.google.com/document/d/1t5WVrj2KQZ2u5s0LvIUtfHnSonBv5Vcv8Gl2k5NXrCQ/edit) whose subjects adhere to -[`duckv1.PodSpecable`](https://github.com/knative/pkg/blob/master/apis/duck/v1/podspec_types.go#L32) +[`duckv1.PodSpecable`](https://github.com/knative/pkg/blob/main/apis/duck/v1/podspec_types.go#L32) easier. The Bindings doc mentions two key elements of the controller architecture: