-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: remove redundant general setting image #195
base: master
Are you sure you want to change the base?
Conversation
### Rationale Since the steps above the image already highlight how to view/modify the default token permission having this image would be redundant.
HI @ad-m can you take a look when you get a chance? Thanks |
@@ -27,13 +27,12 @@ Make sure to save your changes before exiting the settings page. | |||
> [!NOTE] | |||
> | |||
> Granting `Read and write permissions` allows workflows to modify your repository, which can include adding or updating files and code. Always ensure that you trust the workflows you enable with these permissions. | |||
|
|||
|
|||
![General Settings](docs/images/Github_Initial_Git_Push_Settings_General.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can take out the picture, but I would suggest that we describe the location of the settings better.
|
||
![Workflow Settings](docs/images/Github_Initial_Git_Push_Settings_Actions.png) | ||
|
||
The `GITHUB_TOKEN` permissions can also be configured globally for all jobs in a workflow or individually for each job. This example demonstrates how to set the necessary permissions for the `contents` and `pull-requests` scopes on a job level: | ||
The `GITHUB_TOKEN` permissions can also be configured globally for all jobs in a workflow or individually for each job. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you putting a paragraph in here?
Rationale
Since the steps above the image already highlight how to view/modify the default token permission having this image would be redundant.