From 0ed61feed5b3fd421be3197c7e3b7846fb49df3c Mon Sep 17 00:00:00 2001 From: Jens Petersen Date: Sun, 28 Aug 2022 05:11:22 +0000 Subject: [PATCH] create_fedscm_admin_token: mention actual fedora-scm-requests name --- create_fedscm_admin_token.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/create_fedscm_admin_token.md b/create_fedscm_admin_token.md index 6e31696..9550769 100644 --- a/create_fedscm_admin_token.md +++ b/create_fedscm_admin_token.md @@ -1,12 +1,12 @@ # Creating fedscm-admin token for releng -Members of the releng team that are processing the fedora-scm requests are using +Members of the releng team that are processing fedora-scm-requests are using the CLI tool: fedscm-admin. They will need a few access to be able to use this tool properly: - they will need a token to add/adjust things in PDC - they will need a token to create/modify things on src.fp.o -- they will need a token to act on the fedora-scm repo on pagure.io (this one +- they will need a token to act on the fedora-scm-requests repo on pagure.io (this one can be created by themselves once they are given the access) This doc covers the second point.