[work-leas] chore: derive the repository path instead of hardcoding daniel/ #20
Loading…
Reference in a new issue
No description provided.
Delete branch "work-leas-exodus-make-awx-debian-ee-owner-relative"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The image build already tags with
${{ github.repository }}, so published images follow the repository owner. Two places still named the owner literally:.gitea/workflows/renovate.yamlpinnedRENOVATE_REPOSITORIEStodaniel/awx-debian-ee; Renovate would stop finding the repo after an ownership change. Now${{ github.repository }}.scripts/set-renovate-secret.shandscripts/set-renovate-github-token.shhardcoded the admin API path and the prompts. They now derive<owner>/<name>from the checkout's origin URL, withREPO=<owner>/<name>as an override for running outside a checkout.Verified locally:
bash -npasses on both scripts, and the derivation returnsdaniel/awx-debian-eefor the ssh and https remote forms andmossfire/awx-debian-eefor the post-move URL.Prep for the repo namespace move (bead work-leas, epic work-thsk). This repo has no PR-triggered workflow, so there are no CI checks to wait on.
The image build already tags with ${{ github.repository }}, so publishing follows the repo's owner. Two places still named the owner literally: - renovate.yaml pinned RENOVATE_REPOSITORIES to daniel/awx-debian-ee, which would stop matching the repo after an ownership change. - both set-renovate-*.sh scripts hardcoded the admin API path and prompts. Renovate now uses ${{ github.repository }}. The scripts derive <owner>/<name> from the checkout's origin URL and accept REPO=<owner>/<name> as an override. Verified locally: bash -n passes on both scripts, and the derivation returns daniel/awx-debian-ee for both the ssh and https remote forms and mossfire/awx-debian-ee for the post-move URL.