mosaicstack/stack
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 14 Wiki Activity

tools/git/issue-close.sh pins tea login to 'mosaicstack' → fails on USC instance (issue-comment.sh works) #536

New Issue
Closed
opened 2026-06-11 23:22:45 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-06-11 23:22:45 +00:00
Owner
Copy Link

Bug

tools/git/issue-close.sh fails on the USC Gitea instance (git.uscllc.com) with:

login name 'mosaicstack' does not exist

It appears to pin the tea login to mosaicstack regardless of the target repo's host, so closing an issue on a usc/* repo fails. issue-comment.sh works fine on the same repo, so the platform/login detection is inconsistent between the two wrappers.

Context

Found 2026-06-11 closing device-imaging issues on git.uscllc.com. Worked around via the Gitea API fallback (documented path). Same class of login/identity bug as the pr-merge/pr-metadata wrappers fixed in the #524 rollup — issue-close.sh (and likely peers like issue-reopen.sh) appear to have missed that fix.

Fix

Apply the same per-repo login/host detection that issue-comment.sh / detect-platform.sh use (resolve --login/--repo from the target repo's remote host, e.g. usc for git.uscllc.com), rather than a hardcoded mosaicstack login. Audit all issue-*.sh wrappers for the same pattern.

Reported via the device-imaging E2E close-out (installer agent).

## Bug `tools/git/issue-close.sh` fails on the **USC Gitea instance** (git.uscllc.com) with: ``` login name 'mosaicstack' does not exist ``` It appears to pin the `tea` login to `mosaicstack` regardless of the target repo's host, so closing an issue on a `usc/*` repo fails. **`issue-comment.sh` works fine on the same repo**, so the platform/login detection is inconsistent between the two wrappers. ## Context Found 2026-06-11 closing device-imaging issues on git.uscllc.com. Worked around via the Gitea API fallback (documented path). Same class of login/identity bug as the pr-merge/pr-metadata wrappers fixed in the #524 rollup — `issue-close.sh` (and likely peers like `issue-reopen.sh`) appear to have missed that fix. ## Fix Apply the same per-repo login/host detection that `issue-comment.sh` / `detect-platform.sh` use (resolve `--login`/`--repo` from the target repo's remote host, e.g. `usc` for git.uscllc.com), rather than a hardcoded `mosaicstack` login. Audit all `issue-*.sh` wrappers for the same pattern. _Reported via the device-imaging E2E close-out (installer agent)._
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#536
Delete Branch "%!s()"

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?