From 1f8d3e771022578dae7ff1fcc3e4e10904cd295f Mon Sep 17 00:00:00 2001 From: Steven Silvester Date: Mon, 17 Oct 2022 19:37:27 -0500 Subject: [PATCH] update conversion instructions --- docs/source/how_to_guides/convert_repo_from_repo.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/source/how_to_guides/convert_repo_from_repo.md b/docs/source/how_to_guides/convert_repo_from_repo.md index 95ebb11b..5693dbe7 100644 --- a/docs/source/how_to_guides/convert_repo_from_repo.md +++ b/docs/source/how_to_guides/convert_repo_from_repo.md @@ -15,7 +15,9 @@ See [hecklist below for details: ## Checklist for Adoption - [ ] Add a GitHub [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token), preferably from a "machine user" GitHub - account that has write access to the repository. The token will need "public_repo", and "repo:status" permissions. Save the token as `ADMIN_GITHUB_TOKEN` + account that has admin access to the repository. The token itself will + need "public_repo", and "repo:status" permissions. Save the token as + `ADMIN_GITHUB_TOKEN` in the [repository secrets](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository). We need this access token to allow for branch protection rules, which block the pushing of commits when using the `GITHUB_TOKEN`, even when run from an admin user