Skip to content

Commit

Permalink
readme: tip on gh_hook_token generation
Browse files Browse the repository at this point in the history
  • Loading branch information
rr0gi committed Apr 19, 2023
1 parent 0830a56 commit 9b92bf7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Run the `_build/default/src/monorobot.exe` binary. The following commands are su
1. If targeting a private repository, set up a [personal access token](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token) with `repo` scope and store it in the `gh_token` field of the secrets file.
To use the "Project Owners" feature, the token owner must have triage role or above for the repository.
2. [Create a webhook](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/creating-webhooks#setting-up-a-webhook) for the repository you are targeting. Set the *Payload URL* to be `<server_domain>/github`.
3. You can optionally [secure the webhook](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/securing-your-webhooks) with a token, and store it in the `gh_hook_token` field of the secrets file.
3. You can optionally [secure the webhook](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/securing-your-webhooks) with a token (e.g. use `head -c 30 /dev/urandom | base64`), and store it in the `gh_hook_token` field of the secrets file.
4. Configure Slack
1. [Create a Slack app](https://api.slack.com/apps?new_app=1).
2. Click "Install to Workspace", and when prompted to grant permissions to your workspace, click "Allow".
Expand Down

0 comments on commit 9b92bf7

Please sign in to comment.