infrastructure/next-digest
5
0
Fork
You've already forked next-digest
 0
mirror of https://invisible.forgejo.org/infrastructure/next-digest synced 2026-06-15 21:05:24 +00:00
Code Activity
Read-only and used as an action
938 commits 1 branch 6 tags 799 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Forgejo 78c4279b3d update digest from v15.0-test
2026-04-09 02:48:25 +02:00
.forgejo/workflows ci: use data.forgejo.org 2025-11-13 07:58:06 +00:00
digest update digest from v15.0-test 2026-04-09 02:48:25 +02:00
.gitignore add v8.yaml 2024-10-29 19:14:06 +01:00
action.yml fix: do not use vX-instance-template.yaml from the main branch 2025-09-06 14:15:14 +02:00
README.md cleanup: no need for a team forgejo-next-digest is a collaborator 2025-04-29 17:26:15 +02:00
renovate.json Add renovate.json 2024-11-07 15:33:27 +00:00
vX-instance-template.yaml feat: also set vX-instance.yaml 2025-09-02 15:58:56 +02:00

README.md

The content of the digest directory is copied to the k8s-cluster digest directory from the main branch on every push. It will indirectly trigger an update of the matchin v*.next.forgejo.org instance if needed.

The token used to write in this repository must be obtained from the forgejo-next-digest service account, collaborator with write access. It has no known password or valid email. Login as forgejo-next-digest can only be done by reseting the password from the admin interface.

The Forgejo publish workflow is expected to write in this repository using a token obtained from forgejo-next-digest when pushing a new release to the forgejo-experimental organization. For instance:

  - uses: https://invisible.forgejo.org/infrastructure/next-digest@v1.1.0
    with:
      url: https://placeholder:${{ secrets.TOKEN_NEXT_DIGEST }}@invisible.forgejo.org/infrastructure/next-digest
      ref_name: '${{ github.ref_name }}'
      image: 'codeberg.org/forgejo-experimental/forgejo'
      tag_suffix: '-rootless'