momo/create-pull-request
4
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: note push-to-repo classic PAT workflow scope requirement (#3511)

Browse source 
* docs: note `push-to-repo` classic PAT `workflow` scope requirement

Closes https://github.com/peter-evans/create-pull-request/issues/3510

* clarify when workflow scope is necessary

---------

Co-authored-by: Peter Evans <18365890+peter-evans@users.noreply.github.com>
This commit is contained in:
Ville Skyttä 2024-11-25 08:02:41 -01:00 committed by GitHub
parent ce71ba0ccb
commit fb9d3b16d6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/concepts-guidelines.md
View file

@ -231,7 +231,7 @@ It will use their own fork to push code and create the pull request.
1. Create a new GitHub user and login.
2. Fork the repository that you will be creating pull requests in.
3. Create a Classic [Personal Access Token (PAT)](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with `repo` scope.
3. Create a Classic [Personal Access Token (PAT)](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with `repo` scope. If the upstream repository uses GitHub Actions, it's highly likely that you will also need the `workflow` scope.
4. Logout and log back into your main user account.
5. Add a secret to your repository containing the above PAT.
6. As shown in the following example workflow, set the `push-to-fork` input to the full repository name of the fork.