From be8cabe587d2804dac10f9412d3f9c06a15a3426 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Wed, 13 Oct 2021 11:04:16 -0400
Subject: [PATCH] clarify scope of gitlab access token required for branch
 renames

---
 howto/gitlab.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/howto/gitlab.md b/howto/gitlab.md
index ca87d6b7c..3648743cb 100644
--- a/howto/gitlab.md
+++ b/howto/gitlab.md
@@ -438,7 +438,8 @@ GitLab remotes, where it "un-protects" and "re-protects" the branch.
 You should run the script with an account that has "Maintainer" or
 "Owner" access to GitLab, so that it can do the above GitLab API
 changes. You will then need to provide an [access token](https://gitlab.torproject.org/-/profile/personal_access_tokens) through
-the `GITLAB_PRIVATE_TOKEN` environment variable.
+the `GITLAB_PRIVATE_TOKEN` environment variable, which should have the
+scope `api`.
 
 So, for example, this will rename the `master` branch to `main` on the
 local and remote repos:
-- 
GitLab