Setup using the Personal Access Token

This does not need to be done if you chose to set up the SSH deploy keys using the steps above. This method is here for compatibility with the initial approach of this GitHub Action. The Personal Access Token would have access to all your repositories, so if it were to be leaked, the damage would be greater: it would allow pushes to the same repositories to which the Personal Access Token owner has access, and other possible associated permissions. On the other hand, the setup is a bit easier because it does not involve creating the SSH deploy key.

Generate your Personal Access Token using the following steps:

1. Go to the general GitHub Settings (on the right-hand side on the profile picture)

   

2. On the left-hand side pane, scroll to the bottom and click on “Developer Settings”

   

3. Click on “Personal Access Tokens” (also available at https://github.com/settings/tokens)

   

4. Generate a new token entering a name and expiration date, and choose “Repo”. Click the bottom button, “Generate token”. If you choose an expiration date you will need to create a new token after this date. In this example, I have used “No expiration”; this should be used carefully.

   

5. Copy the displayed token

   

Then make the token available to the GitHub Action using the following steps:

1. Go to the GitHub page for the source repository (origin repository). Click on “Settings” for the repository

   

2. Click on “New repository secret”

   

3. Name: “API_TOKEN_GITHUB”

4. Value: paste the token that you copied earlier

5. Click on “Add secret”