Add input documentation #21
Conversation
README.md
Outdated
| | Name | Type | Description | | ||
| |--------------------|---------|-----------------------------------| | ||
| | `add_labels` | String | Comma separated list of labels to add to the backport PR. | | ||
| | `github_token` | String | Token for the GitHub API. Set this to a personal access token (PAT) if you want github workflows to run on the opened PR. | |
There was a problem hiding this comment.
This is pretty good, thanks! Wondering, do you know what exact permissions the PAT needs? Is giving repository access enough?
There was a problem hiding this comment.
If I remember correctly, yes. Would be nice to add this as well.
There was a problem hiding this comment.
also thanks from the MapServer team! (this action is excellent) thanks again.
There was a problem hiding this comment.
Trying to figure out how to run the github actions on the backport PRs, I've stumbled into more issues... I did give the backport bot PAT repository access, and marked the user as collaborator to the project, but eventulaly got:
remote: Permission to geoserver/geoserver.git denied to geoserver-bot.
fatal: unable to access 'https://github.com/geoserver/geoserver.git/': The requested URL returned error: 403
I did give it read permissions (thought it was enough since random users with no permissions at all can open PRs), now I'm trying with Triage permissions. Do you remember what kind of relationship was setup betwene qgis-bot and the QGIS project?
There was a problem hiding this comment.
The backport branch will be created in the base repository, so the user will need to be able to create branches there too.
There was a problem hiding this comment.
Oh ok... I'm not sure Triage will work then, says "manage PRs" but does not talk about creating branches. Maybe I need to give it "write" permissions instead.
There was a problem hiding this comment.
Confirmed, the PAT needs repo access and the user has to be added as a collaborator, with write permissions.
I've shared the secret as a "repository secret" in order to make the action yaml work as written, although I believe it would be possible to make it an environment secret too, by changing the action and make it run in that same environment.
There was a problem hiding this comment.
Thank you for the feedback. Adjusted accordingly.
No description provided.