You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,11 @@ contents:
34
34
Then, add a `./github/virtual-assistant.yml` with the configuration as described
35
35
below.
36
36
37
+
if you use repository-based projects, `${{ secrets.GITHUB_TOKEN }}` provides appropriate access privileges to this GitHub action. For organization-based projects the default GitHub token might not be enough so you need to follow these steps
38
+
1.[Create](https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) a new personal github access token by enabling `repo` and `admin:org` permissions. Copy the value of the created token
39
+
2. Create a new project secret under ( `https://github.com/elastic/YOUR_PROJECT/settings/secrets` ). Name it as you want (for instance `ACTIONS_TOKEN`) and paste the value of the personal access token you created in step 1.
40
+
3. Replace `${{ secrets.GITHUB_TOKEN }}` with `${{ secrets.ACTIONS_TOKEN }}` in your yml configuration
41
+
37
42
## Configuration
38
43
39
44
Configuration can be stored at `./github/virtual-assistant.yml` as below
0 commit comments