forgejo/.forgejo/workflows
Earl Warren a23de662eb chore(ci): set the milestone when a pull request is closed (take 4)
The milestone can only be determined to be final when a pull request
is merged.

It is possible that a pull request is opened during the development of
v10 and merged after it is published.

It is also possible that it is permanently closed without being merged.

(cherry picked from commit 6f53f7d007)
2024-12-10 06:21:21 +00:00
..
backport.yml chore(ci): ROLE forgejo-coding & forgejo-testing 2024-11-14 10:19:49 +01:00
build-release-integration.yml chore(ci): ROLE forgejo-coding & forgejo-testing 2024-11-14 10:19:49 +01:00
build-release.yml fix(release): add missing ARG RELEASE_VERSION 2024-04-17 16:06:43 +00:00
cascade-setup-end-to-end.yml chore(ci): ROLE forgejo-coding & forgejo-testing (part two) 2024-11-14 10:21:29 +01:00
e2e.yml chore(ci): ROLE forgejo-coding & forgejo-testing (part two) 2024-11-14 10:21:29 +01:00
milestone.yml chore(ci): set the milestone when a pull request is closed (take 4) 2024-12-10 06:21:21 +00:00
mirror.yml [CI] mirror to forgejo-integration daily instead of each commit 2024-02-17 11:55:52 +01:00
publish-release.yml chore(ci): remove unused experimental DNS updates 2024-11-20 16:07:33 +00:00
renovate.yml chore(ci): ROLE forgejo-coding & forgejo-testing 2024-11-14 10:19:49 +01:00
testing.yml chore(ci): ROLE forgejo-coding & forgejo-testing (part two) 2024-11-14 10:21:29 +01:00