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, member of the next-digest team. 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://code.forgejo.org/infrastructure/next-digest@v1.0.0
    with:
      url: https://placeholder:${{ secrets.TOKEN_NEXT_DIGEST }}@code.forgejo.org/infrastructure/next-digest
      ref_name: '${{ github.ref_name }}'
      image: 'codeberg.org/forgejo-experimental/forgejo'
      tag_suffix: '-rootless'