From b3726d28f01a80d0f56230d957b822d772d43f62 Mon Sep 17 00:00:00 2001
From: Helio Machado <0x2b3bfa0+git@googlemail.com>
Date: Sat, 16 Oct 2021 13:27:17 +0000
Subject: [PATCH] Convert repo_token to uppercase

---
 content/docs/self-hosted-runners.md | 10 +++++-----
 content/docs/usage.md               |  4 ++--
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/content/docs/self-hosted-runners.md b/content/docs/self-hosted-runners.md
index 6b6dad85..2387657d 100644
--- a/content/docs/self-hosted-runners.md
+++ b/content/docs/self-hosted-runners.md
@@ -238,12 +238,12 @@ Use either:
 For instance, to use a personal access token:
 
 1. Navigate to **User Settings** &rightarrow; **Access Tokens**
-   - in the "Name" field, type `repo_token`
+   - in the "Name" field, type `REPO_TOKEN`
    - select `api`, `read_repository` and `write_repository`
    - click "Create personal access token" and copy it
 2. In your GitLab project, navigate to **Settings** &rightarrow; **CI/CD**
    &rightarrow; **Variables** &rightarrow; **Add Variable**
-   - in the "Key" field, type `repo_token`
+   - in the "Key" field, type `REPO_TOKEN`
    - in the "Value" field, paste your Personal Access Token
    - select "Mask variable"
    - deselect "Protect variable"
@@ -255,7 +255,7 @@ credentials.
 </tab>
 <tab title="Bitbucket">
 
-Bitbucket Cloud does not use access tokens. Instead, create a `repo_token`
+Bitbucket Cloud does not use access tokens. Instead, create a `REPO_TOKEN`
 variable with a Base64 encoded username and password.
 
 Use either:
@@ -268,7 +268,7 @@ Use either:
   intended use case: you limit the account to only access the repositories where
   you plan to deploy runners to.
 
-In either case, the steps to create a `repo_token` are:
+In either case, the steps to create a `REPO_TOKEN` are:
 
 1. Use a Base64 encoder of your choice to encode a Bitbucket username and
    password:
@@ -276,7 +276,7 @@ In either case, the steps to create a `repo_token` are:
    - copy the resulting Base64 token
 2. In your repository, go to **Repository Settings** &rightarrow; **Repository
    Variables**
-   - in the "Name" field, type `repo_token`
+   - in the "Name" field, type `REPO_TOKEN`
    - in the "Value" field, paste the Base64 token
    - select `Secured` to hide credentials in all Bitbucket logs
 
diff --git a/content/docs/usage.md b/content/docs/usage.md
index 621f6206..5720df7b 100644
--- a/content/docs/usage.md
+++ b/content/docs/usage.md
@@ -86,7 +86,7 @@ create-CML-report:
 
 ⚠️ You _must_ provide a
 [personal or project access token (PAT)](/doc/self-hosted-runners#personal-access-token)
-via a `repo_token` variable.
+via a `REPO_TOKEN` variable.
 
 The example above generates visual reports in merge requests:
 [![](/img/GitLab_CML_report.png '=400')](https://gitlab.com/iterative.ai/cml-base-case/-/merge_requests/3)
@@ -131,7 +131,7 @@ pipelines:
 
 ⚠️ You _must_ provide
 [access credentials](/doc/self-hosted-runners#personal-access-token) via a
-`repo_token` variable.
+`REPO_TOKEN` variable.
 
 The example above generates visual reports in pull requests:
 [![](/img/bitbucket_cloud_pr.png '=600')](https://bitbucket.org/iterative-ai/cml-base-case/pull-requests/2)