This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
Update setting personal access token (PAT) instruction #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mohammad-oghli
commented
Aug 20, 2023
README.md
Outdated
| @@ -22,7 +22,7 @@ Please complete the instructions below: | |||
|
|
|||
| 1. Create an organization-owned copy of this repository using the [Use this template](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template#creating-a-repository-from-a-template) button. | |||
| 2. Create a personal access token (PAT) of type **classic tokens** with the `read:org` and `write:org` scope selected. | |||
| 3. Store the PAT as an [organization secret](https://docs.github.com/en/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-an-organization) titled `EXERCISE_PAT`. We recommend making the secret available only to your newly created repository. | |||
| 3. Store the PAT as an [organization secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) titled `EXERCISE_PAT` in actions tab. We recommend making the secret available only to your newly created repository. | |||
There was a problem hiding this comment.
Storing the PAT as organization secret should be for a repository on actions tab and not for codespaces #26
mohammad-oghli
commented
Aug 20, 2023
| @@ -22,7 +22,7 @@ Please complete the instructions below: | |||
|
|
|||
| 1. Create an organization-owned copy of this repository using the [Use this template](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template#creating-a-repository-from-a-template) button. | |||
| 2. Create a personal access token (PAT) of type **classic tokens** with the `read:org` and `write:org` scope selected. | |||
| 3. Store the PAT as an [organization secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) titled `EXERCISE_PAT` in actions tab. We recommend making the secret available only to your newly created repository. | |||
| 3. Store the PAT as an [organization secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) titled `EXERCISE_PAT` in actions tab. We recommend making the secret available only to your newly created repository. Then go to organizaion setting and from **Actions** tab -> **General** set the Workflow permissions to `read and write permissions`. | |||
There was a problem hiding this comment.
This step should be done in organization setting in actions tab #26
mohammad-oghli
commented
Aug 20, 2023
| @@ -21,7 +21,7 @@ This exercise checks your ability to manage GitHub Apps for your organization. I | |||
| Please complete the instructions below: | |||
|
|
|||
| 1. Create an organization-owned copy of this repository using the [Use this template](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template#creating-a-repository-from-a-template) button. | |||
| 2. Create a personal access token (PAT) with the `read:org` scope selected. | |||
| 2. Create a personal access token (PAT) of type **classic tokens** with the `read:org` and `write:org` scope selected. | |||
There was a problem hiding this comment.
Select classic tokens and add write scope #26
|
please review the PR @hectorsector |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The instruction for creating personal access tokens need to be updated using classic tokens type and adding write scope to the permissions #26