serv/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-26 05:33:52 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

chore(docs): explain vars.SKIP_END_TO_END when building a release

Browse source
This commit is contained in:
Earl Warren 2024-12-24 06:52:31 +01:00
parent 5f685bf069
commit 92b770326f
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
.forgejo/workflows/build-release.yml
View file

@ -14,6 +14,12 @@
# secrets.CASCADE_DESTINATION_TOKEN: <generated from code.forgejo.org/forgejo-ci> scope read:user, write:repository, write:issue # secrets.CASCADE_DESTINATION_TOKEN: <generated from code.forgejo.org/forgejo-ci> scope read:user, write:repository, write:issue
# vars.CASCADE_DESTINATION_DOER: forgejo-ci # vars.CASCADE_DESTINATION_DOER: forgejo-ci
# #
# vars.SKIP_END_TO_END: `true` or `false`
# It must be `false` (or absent) so https://code.forgejo.org/forgejo/end-to-end is run
# with the newly built release.
# It must be set to `true` when a release is missing, for instance because it was
# removed and failed to upload.
#
on: on:
push: push:
tags: 'v[0-9]+.[0-9]+.*' tags: 'v[0-9]+.[0-9]+.*'