devastator
68d92069c5
Core Build (push) / self-test (push) Successful in 11s
+ documentation updated
27 lines
1.4 KiB
Markdown
27 lines
1.4 KiB
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.
|
|
|
|
The workflow (or jobs individually) needs to define an env variable `ACTI_BOT_TOKEN` with the bots token (as secrets do not automatically propagate into composite action context, at least it didn't work while testing).
|
|
|
|
## Publish
|
|
|
|
Publishes a `generic` package to current Gitea instance. Example:
|
|
|
|
```yaml
|
|
- uses: https://source.vague.tech/open-vague/ci-actions/publish@feature/1-publish
|
|
with:
|
|
file: some-content.json
|
|
package: the-package
|
|
version: master
|
|
force: true
|
|
```
|
|
|
|
* `file` - path to the file to upload (used as uploaded file name within the package)
|
|
* `package` - the package name
|
|
* `version` - the package version, need to be unique (unless force flag is set)
|
|
* `force` - false by default; if set **deletes the whole version** of the package (all files) and then publishes instead with the same version |