Earl Warren 2a78dba95b chore(ci): trigger a mirror when a release is publish ... Notify https://code.forgejo.org/forgejo/forgejo that a new release was published by setting the trigger label to https://code.forgejo.org/forgejo/forgejo/issues/5. It is only ever useful when a stable release is published, the experimental releases are not mirrored. But it is triggered in all cases. This will waste a few mirror check daily, when experimental releases are built. This is an improvement compared to the current situation where mirrors are checked hourly: * Instead of being checked 24 times per day it will be down to less than 5 * The mirror happens immediately after the release is published instead of waiting for the next run of the cron job. If a mirror operation is in progress, as evidenced by the presence of the trigger label on the issure, it means two releases are being published. Wait up to 1h for the mirror to complete and remove the trigger label. (cherry picked from commit 7492330721)		2024-11-13 16:53:43 +00:00
..
issue_template	docs: add a PR checklist template (#4564)	2024-07-22 05:23:54 +00:00
testdata/build-release	forgejo-cli is now a symlink and cannot be used for sanity checks	2024-10-17 06:00:05 +00:00
workflows	chore(ci): trigger a mirror when a release is publish	2024-11-13 16:53:43 +00:00
cascading-pr-end-to-end	chore(ci): optimize end-to-end runs	2024-08-08 17:53:12 +02:00
cascading-release-end-to-end	chore(ci): optimize end-to-end runs	2024-08-08 17:53:12 +02:00
pull_request_template.md	Replace Developer Guide links with the new Contributor Guide one for PR template and release workflows comments.	2024-08-26 14:29:10 +03:00