devastator
de8ccc6fcb
Core Build (push) / self-test (push) Failing after 11s
+ docs + more auth tests
9 lines
714 B
Markdown
9 lines
714 B
Markdown
# gitea-actions
|
|
|
|
## Setup
|
|
|
|
For these actions to work properly one needs a bot account for the token. So, once the bot account is created, generate a token for it with `repository:write` and `package:write` permissions. However that's not enough, even making the bot a repository collaborator is not enough. The bot needs to have permissions on the organization level.
|
|
|
|
The recommended way is to create a team in the organization that has access to all repositories and set `Releases:Write` and `Packages:Write` permissions and `Read` for all the rest (yet, strictly speaking that's not necessary) and add the bot to the team.
|
|
|
|
Add an organization level secret called `ACTI_BOT_TOKEN` with the bot's token as value. |