Clarify scopes needed for admin token

Author: Steven Silvester

docs/source/get_started/making_first_release.md

@@ -12,7 +12,7 @@ already uses Jupyter Releaser.
 
 - Fork `jupyter_releaser`
 - Generate 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
-- Add 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) of your fork.
+- Add 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) of your fork.  The token must have `repo` and `workflow` scopes.
 - If the repo generates PyPI release(s), create a scoped PyPI [token](https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#saving-credentials-on-github). We recommend using a scoped token for security reasons.
 - You can store the token as `PYPI_TOKEN` in your fork's `Secrets`.