privacy-in-design/gitea-migration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: add validation for comma-separated repos in registration token resolution

Browse Source
This commit is contained in:
S
2026-03-02 09:15:47 -05:00
parent b22a95522b
commit 7bf3a1bfd5
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
manage_runner.sh
View File

@@ -217,9 +217,17 @@ build_runner_labels() {
# Resolve registration token based on repos field. # Resolve registration token based on repos field.
# repos=all → instance-level token from .env # repos=all → instance-level token from .env
# repos=<name> → fetch repo-level token from Gitea API # repos=<name> → fetch repo-level token from Gitea API
# Comma-separated repos are NOT supported here — configure_runners.sh
# expands them into separate INI sections before they reach this point.
# Sets RUNNER_REG_TOKEN. # Sets RUNNER_REG_TOKEN.
# --------------------------------------------------------------------------- # ---------------------------------------------------------------------------
resolve_registration_token() { resolve_registration_token() {
if [[ "$RUNNER_REPOS" == *,* ]]; then
log_error "Runner '$RUNNER_NAME': repos='$RUNNER_REPOS' contains commas."
log_error " Each act_runner process can only register to one repo."
log_error " Run ./setup/configure_runners.sh to expand into separate runner sections."
return 1
fi
if [[ "$RUNNER_REPOS" == "all" ]] || [[ -z "$RUNNER_REPOS" ]]; then if [[ "$RUNNER_REPOS" == "all" ]] || [[ -z "$RUNNER_REPOS" ]]; then
RUNNER_REG_TOKEN="${GITEA_RUNNER_REGISTRATION_TOKEN:-}" RUNNER_REG_TOKEN="${GITEA_RUNNER_REGISTRATION_TOKEN:-}"
else else