Skip to content

fix(ci3): GITHUB_REPOSITORY unbound when running ci.sh locally (v5-next) - #24060

Merged
charlielye merged 1 commit into
v5-nextfrom
ci3-fix-github-repository-unbound-v5
Jun 12, 2026
Merged

fix(ci3): GITHUB_REPOSITORY unbound when running ci.sh locally (v5-next)#24060
charlielye merged 1 commit into
v5-nextfrom
ci3-fix-github-repository-unbound-v5

Conversation

@charlielye

Copy link
Copy Markdown
Contributor

Port of the unbound-variable fix (see #24059).

The repo-scoped instance name added repo=${GITHUB_REPOSITORY##*/} then repo=${repo:-aztec-packages}. Under set -u (set by ci3/source), ##*/ on an unset GITHUB_REPOSITORY aborts before the default applies, so any local ./ci.sh <cmd> fails with GITHUB_REPOSITORY: unbound variable. CI always has it set, so it passed there.

Fix: default first, then strip — repo=${GITHUB_REPOSITORY:-aztec-packages}; repo=${repo##*/} — in ci.sh and ci3/bootstrap_ec2. Instance-name scheme unchanged.

…locally

The repo-scoped instance name added `repo=${GITHUB_REPOSITORY##*/}` followed by
`repo=${repo:-aztec-packages}`. Under `set -u` (set by ci3/source), the `##*/`
expansion on an unset GITHUB_REPOSITORY aborts before the default on the next line
applies — so any local `./ci.sh <cmd>` fails with "GITHUB_REPOSITORY: unbound
variable". It only surfaced locally; CI always has GITHUB_REPOSITORY set.

Default first, then strip: `repo=${GITHUB_REPOSITORY:-aztec-packages}; repo=${repo##*/}`.
Same fix in ci.sh and ci3/bootstrap_ec2.
@charlielye
charlielye merged commit d0b2452 into v5-next Jun 12, 2026
7 of 9 checks passed
@charlielye
charlielye deleted the ci3-fix-github-repository-unbound-v5 branch June 12, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant