siim/Bullosseum
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Drop the stale GitHub-workflow reference from the Gitea CI header

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017KoYBYQgRyY1zDHXMsXY3V
This commit is contained in:
Richard Aasa
2026-09-06 01:31:29 +03:00
parent 64a8a9863d
commit 9ca6f282f5
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/ci.yml
+5 -5
View File
@@ -2,11 +2,11 @@ name: CI
# Gitea Actions is GitHub-Actions-compatible: drop this in .gitea/workflows/, enable Actions on the # Gitea Actions is GitHub-Actions-compatible: drop this in .gitea/workflows/, enable Actions on the
# repo ([actions] ENABLED=true in app.ini, Gitea >= 1.19) and register an act_runner — it then runs # repo ([actions] ENABLED=true in app.ini, Gitea >= 1.19) and register an act_runner — it then runs
# on every push / PR just like the GitHub workflow. This mirrors .github/workflows/ci.yml but installs # on every push / PR. Godot and gdtoolkit are installed with plain shell steps (not the chickensoft
# Godot and gdtoolkit with plain shell steps instead of the chickensoft setup-godot action, because a # setup-godot action), because a self-hosted runner usually can't reach the GitHub action registry
# self-hosted runner usually can't reach the GitHub action registry (unless DEFAULT_ACTIONS_URL is set # (unless DEFAULT_ACTIONS_URL is set to proxy github.com). Only actions/checkout and upload-artifact
# to proxy github.com). Only actions/checkout and actions/upload-artifact remain as external actions — # remain as external actions — both ship with Gitea's default proxy; if yours is offline, mirror them
# both ship with Gitea's default proxy; if yours is offline, mirror them into your instance. # into your instance.
# #
# It also runs once a day (schedule) as a safety net over main's tip. The `guard` job skips that daily # It also runs once a day (schedule) as a safety net over main's tip. The `guard` job skips that daily
# run when the commit already passed — so an idle main isn't re-tested, but a commit whose push-time # run when the commit already passed — so an idle main isn't re-tested, but a commit whose push-time