dynamically populate the correct repo branch (#1945)

Author: RichieEscarez

docs/eventing/README.md

@@ -307,7 +307,7 @@ Knative Serving application so that they can be consumed.
       certificate.
 
 See the
-[Kafka Source](https://github.com/knative/eventing-contrib/tree/master/kafka/source)
+[Kafka Source](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/kafka/source)
 example.
 
 ### CamelSource
@@ -337,7 +337,7 @@ to be installed into the current namespace.
   development purposes.
 
 See the
-[CamelSource](https://github.com/knative/eventing-contrib/tree/master/camel/source/samples)
+[CamelSource](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/camel/source/samples)
 example.
 
 ## Getting Started

docs/eventing/broker-trigger.md

@@ -90,7 +90,7 @@ to that `Broker`. If `spec.channelTemplateSpec` is not specified, then the
 
 Have a `Channel` CRD installed and set as the default channel for the namespace
 you are interested in. For development, the
-[InMemoryChannel](https://github.com/knative/eventing/tree/master/config/channels/in-memory-channel)
+[InMemoryChannel](https://github.com/knative/eventing/tree/{{< branch >}}/config/channels/in-memory-channel)
 is normally used.
 
 #### Changing

docs/eventing/channels/channels-crds.md

@@ -27,8 +27,8 @@ Notes:
 Name | Status | Support | Description
 --- | --- | --- | ---
 [GCP PubSub](https://github.com/google/knative-gcp) | Proof of Concept | None | Channels are backed by [GCP PubSub](https://cloud.google.com/pubsub/).
-[InMemoryChannel](https://github.com/knative/eventing/tree/master/config/channels/in-memory-channel) | Proof of Concept | None | In-memory channels are a best effort Channel. They should NOT be used in Production. They are useful for development.
-[KafkaChannel](https://github.com/knative/eventing-contrib/tree/master/kafka/channel/config) | Proof of Concept | None | Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics.
-[NatssChannel](https://github.com/knative/eventing/tree/master/contrib/natss/config) | Proof of Concept | None | Channels are backed by [NATS Streaming](https://github.com/nats-io/nats-streaming-server#configuring).
+[InMemoryChannel](https://github.com/knative/eventing/tree/{{< branch >}}/config/channels/in-memory-channel) | Proof of Concept | None | In-memory channels are a best effort Channel. They should NOT be used in Production. They are useful for development.
+[KafkaChannel](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/kafka/channel/config) | Proof of Concept | None | Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics.
+[NatssChannel](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/natss/config) | Proof of Concept | None | Channels are backed by [NATS Streaming](https://github.com/nats-io/nats-streaming-server#configuring).
 
 

docs/eventing/channels/channels.yaml

@@ -1,19 +1,19 @@
 # List of available Channel implementation for persistence of the events associated with a given channel 
 channels:
   - name: InMemoryChannel
-    url: https://github.com/knative/eventing/tree/master/config/channels/in-memory-channel
+    url: https://github.com/knative/eventing/tree/{{< branch >}}/config/channels/in-memory-channel
     status: Proof of Concept
     support: None
     description: >
       In-memory channels are a best effort Channel. They should NOT be used in Production. They are useful for development.
   - name: KafkaChannel
-    url: https://github.com/knative/eventing-contrib/tree/master/kafka/channel/config
+    url: https://github.com/knative/eventing-contrib/tree/{{< branch >}}/kafka/channel/config
     status: Proof of Concept
     support: None
     description: >
       Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics.
   - name: NatssChannel
-    url: https://github.com/knative/eventing/tree/master/contrib/natss/config
+    url: https://github.com/knative/eventing-contrib/tree/{{< branch >}}/natss/config
     status: Proof of Concept
     support: None
     description: >

docs/eventing/debugging/README.md

@@ -144,7 +144,7 @@ This should return a single Pod, which if you inspect is the one generated by
 ##### `chan`
 
 `chan` uses the
-[`in-memory-channel`]( https://github.com/knative/eventing/tree/master/config/channels/in-memory-channel).
+[`in-memory-channel`]( https://github.com/knative/eventing/tree/{{< branch >}}/config/channels/in-memory-channel).
 This is a very basic channel and has few
 failure modes that will be exhibited in `chan`'s `status`.
 

docs/eventing/event-registry.md

@@ -258,7 +258,7 @@ the next topic: How do we actually populate the registry in the first place?
 
   If you are interested in more information regarding configuration options of a
   KafkaSource, please refer to the
-  [KafKaSource example](https://github.com/knative/eventing-contrib/tree/master/kafka/source/samples).
+  [KafKaSource example](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/kafka/source/samples).
 
   For this discussion, the relevant information from the yaml above are the
   `sink` and the `topics`. We observe that the `sink` is of kind `Broker`. We

docs/eventing/getting-started.md

@@ -34,7 +34,7 @@ If the `knative-eventing` namespace or the `imc-controller-*` does not exist, us
 
 1. Make sure that you have a functioning Kubernetes cluster. See the [Comprehensive Install guide](../install) for more information.
    - Old versions of Knative Serving doesn't necessarily work well with latest Knative Eventing, so try to install the latest version of Knative Serving.
-   - If your Kubernetes cluster comes with pre-installed Istio, make sure it has `cluster-local-gateway` [deployed](https://github.com/knative/serving/blob/master/DEVELOPMENT.md#deploy-istio). Depending on which Istio version you have, you'd need to apply the `istio-knative-extras.yaml` in the corresponding version folder at [here](https://github.com/knative/serving/tree/master/third_party).
+   - If your Kubernetes cluster comes with pre-installed Istio, make sure it has `cluster-local-gateway` [deployed](https://github.com/knative/serving/blob/master/DEVELOPMENT.md#deploy-istio). Depending on which Istio version you have, you'd need to apply the `istio-knative-extras.yaml` in the corresponding version folder at [here](https://github.com/knative/serving/tree/{{< branch >}}/third_party).
 2. Install the Eventing CRDs by running the following command:
 
     ```sh

docs/eventing/samples/container-source/README.md

@@ -175,6 +175,5 @@ event source is a sample for your reference.
 
 When the container image is ready, a YAML file will be used to create a concrete
 ContainerSource. Use [heartbeats-source.yaml](./heartbeats-source.yaml) as a
-sample for reference. You can get more details about ContainerSource
-specification
-[here](https://github.com/knative/docs/tree/master/docs/eventing#containersource).
+sample for reference. [Learn more about the ContainerSource
+specification](../../../eventing#containersource).

docs/eventing/samples/kubernetes-event-source/README.md

@@ -5,18 +5,22 @@ weight: 50
 type: "docs"
 ---
 
-Kubernetes Event Source example shows how to wire kubernetes cluster events for
-consumption by a function that has been implemented as a Knative Service. The
-code for the following files can be found in the
-[/kubernetes-event-source/](https://github.com/knative/docs/tree/master/docs/eventing/samples/kubernetes-event-source)
-directory.
+Kubernetes Event Source example shows how to wire Kubernetes cluster events for
+consumption by a function that has been implemented as a Knative Service. 
 
-## Deployment Steps
+## Before you begin
+
+1. You must have a Knative cluster running both the Serving and Eventing components.
+   To learn how to install the required components, see [Installing Knative](../../../install).
+1. You can follow the steps below to create new files, or you clone a copy from
+   the repo by running:
 
-### Prerequisites
+   ```shell
+   git clone -b "release-0.9" https://github.com/knative/docs knative-docs
+   cd knative-docs/docs/eventing/samples/kubernetes-event-source
+   ```
 
-1. Setup [Knative Serving](../../../serving).
-1. Setup [Knative Eventing](../../../eventing).
+## Deployment Steps
 
 ### Broker
 

docs/eventing/samples/writing-a-source/03-reconcile-sources.md

@@ -114,9 +114,9 @@ string.
 
 _After completing this tutorial, consider replacing the code below with existing
 sink resolution helpers provided by Knative: `AddressableType` from
-`[github.com/knative/pkg/apis/duck/v1alpha1](https://github.com/knative/pkg/tree/master/apis/duck/v1alpha1)`
+`[github.com/knative/pkg/apis/duck/v1alpha1](https://github.com/knative/pkg/tree/{{< branch >}}/apis/duck/v1alpha1)`
 and `GetSinkURI` from
-`[github.com/knative/eventing-contrib/pkg/controller/sinks](https://github.com/knative/eventing-contrib/tree/master/pkg/controller/sinks)`._
+`[github.com/knative/eventing-contrib/pkg/controller/sinks](https://github.com/knative/eventing-contrib/tree/{{< branch >}}/pkg/controller/sinks)`._
 
 ```go
 type addressableType struct {