Earl Warren d257fa179b [CI] do not hardcode the Forgejo release in end-to-end testing ... Now that Forgejo has its own release number, use the Makefile as a reference. Also document and improve support for debugging this pull_request_target workflow by using a branch in the repository.		2024-03-06 03:15:07 +08:00
..
build-release-integration.yml	[CI] name the test release after the latest v*-dev tag	2024-02-23 15:37:46 +01:00
build-release.yml	[CI] name the test release after the latest v*-dev tag	2024-02-23 15:37:46 +01:00
cascade-setup-end-to-end.yml	[CI] do not hardcode the Forgejo release in end-to-end testing	2024-03-06 03:15:07 +08:00
e2e.yml	[CI] Forgejo Actions e2e tests (squash) generate	2024-02-05 13:33:59 +01:00
mirror.yml	[CI] mirror to forgejo-integration daily instead of each commit	2024-02-17 11:55:52 +01:00
publish-release.yml	[RELEASE] publish container images tagged with the major version	2024-03-02 19:48:28 +08:00
testing.yml	[CI] run frontend checks	2024-02-25 23:08:09 +01:00