Merge pull request #30 from geerteltink/docs/explain-scope

Explain the needed scopes for the admin token

Author: Ocramius

README.md

@@ -29,8 +29,8 @@ to your project or organization:
 - `SIGNING_SECRET_KEY` - a **password-less** private GPG key in ASCII format, to be used for signing your releases:
   please use a dedicated GPG subkey for this purpose. Unsigned releases are not supported, and won't be supported.
 - `ORGANIZATION_ADMIN_TOKEN` - if you use the file from [`examples/.github/workflows/release-on-milestone-closed.yml`](examples/.github/workflows/release-on-milestone-closed.yml),
-  then you have to provide a `ORGANIZATION_ADMIN_TOKEN`, which is a github token with administrative rights over
-  your organization (issued by a user that has administrative rights over your project).
+  then you have to provide a `ORGANIZATION_ADMIN_TOKEN` (with a full repo scope), which is a github token with
+  administrative rights over your organization (issued by a user that has administrative rights over your project).
   This is required for the `laminas:automatic-releases:switch-default-branch-to-next-minor`
   command, because [changing default branch of a repository currently requires administrative token rights](https://developer.github.com/v3/repos/#update-a-repository).
   You can generate a token from your [personal access tokens page](https://github.com/settings/tokens/new).