Skip to content

fix(triage): count builds from origin/code/cash and load .env.local for the event fetch - #1667

Merged
bmc08gt merged 1 commit into
code/cashfrom
fix/triage-skill-scripts
Oct 2, 2026
Merged

bmc08gt merged 1 commit into
code/cashfrom
fix/triage-skill-scripts

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

build-lookup.sh counted commits from the local HEAD, so on a checkout behind origin it rejected a real build: versionCode 4718 failed with "exceeds current commit count (4700)". Builds are cut from code/cash, so the script now fetches and counts from origin/code/cash. --ref <ref> counts from somewhere else. The offset maths assumes linear history, so the script now also checks that the resolved commit has exactly N ancestors and fails if not, instead of returning the wrong commit.

Step 2 of the triage skill told the agent to source only .env before fetching event_url. bugsnag-top.sh also reads .env.local, which is where the token is set, so the manual fetch went out without a token. The step now loads both files in the same shell as the request.

The event URL problem from the same triage was already fixed by #1646.

…or the event fetch

build-lookup.sh counted commits from the local HEAD, so on a checkout behind
origin it rejected a real build (4718 against a local count of 4700). It now
fetches and counts from origin/code/cash, the branch builds are cut from, with
--ref to override, and checks that the resolved commit has exactly N ancestors.

The triage skill's manual event fetch told the agent to source only .env, while
bugsnag-top.sh also reads .env.local, where the token lives.
@bmc08gt bmc08gt self-assigned this Oct 2, 2026
@github-actions github-actions Bot added the type: fix Bug fix label Oct 2, 2026
@bmc08gt
bmc08gt merged commit 83f7be6 into code/cash Oct 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: fix Bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant