How
Using the git-mirror.yaml or https://git-mirror.forgejo.org/, we can extract all available actions on data.forgejo.org, and add them in a nicely formatted list, e.g. in docs/user/actions/forgejo-hosted.md.
Implementation
- workflow on /forgejo/k8s-cluster:
➖ needs write access to docs
➕ can run on push to main
- workflow on /forgejo/docs:
➕ needs to write only to self
➖ needs to be triggered, but can do with cron, e.g. once a day
Expected output
- list of all actions with links to mirror, or
- table with additional information, e.g. last update, latest version, what it does?, etc. – requires to scan through all git mirrors.
Alternatives
Create a landing page for data.forgejo.org with this information.
Related
forgejo/discussions#365
### How
Using the [`git-mirror.yaml`](https://codeberg.org/forgejo/k8s-cluster/src/branch/main/flux/apps/forgejo-code/git-mirror.yaml) or https://git-mirror.forgejo.org/, we can extract all available actions on data.forgejo.org, and add them in a nicely formatted list, e.g. in [[docs/user/actions/forgejo-hosted.md]].
### Implementation
1. workflow on [[/forgejo/k8s-cluster]]:
➖ needs write access to docs
➕ can run on push to main
2. workflow on [[/forgejo/docs]]:
➕ needs to write only to self
➖ needs to be triggered, but can do with cron, e.g. once a day
### Expected output
- list of all actions with links to mirror, or
- table with additional information, e.g. last update, latest version, what it does?, etc. – requires to scan through all git mirrors.
### Alternatives
Create a landing page for data.forgejo.org with this information.
### Related
forgejo/discussions#365