You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/how_to_guides/convert_repo_from_repo.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,10 @@ See [checklist](#Checklist-for-Adoption) below for details:
14
14
15
15
## Checklist for Adoption
16
16
17
-
-[ ] Add a [GitHub Access token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with access to target GitHub repo to run GitHub Actions, saved as
18
-
`ADMIN_GITHUB_TOKEN` in the [repository secrets](https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).
19
-
The token needs to have `public_repo` and `repo:status` permissions.
20
17
-[ ] Add access token for the [PyPI registry](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#saving-credentials-on-github) stored as `PYPI_TOKEN`.
21
18
_Note_ For security reasons, it is recommended that you scope the access
22
-
to a single repository.
19
+
to a single repository. Additionally, this token should belong to a
20
+
bot account and not a single user.
23
21
-[ ] If needed, add access token for [npm](https://docs.npmjs.com/creating-and-viewing-access-tokens), saved as `NPM_TOKEN`.
24
22
-[ ] Ensure that only trusted users with 2FA have admin access to the
25
23
repository, since they will be able to trigger releases.
0 commit comments