shockbot

ShockVPN/shockbot

Fork 0

Commit Graph

Author	SHA1	Message	Date
Colin McDonnell	d1e075fa3b	fix npx binary resolution: run in workspace, not action directory npx was running with cwd set to the action's own directory, which has package.json with "name": "pullfrog". npm treats the local package as satisfying the request and skips the registry fetch, then fails to find the binary (sh: 1: pullfrog: not found). use GITHUB_WORKSPACE instead. Made-with: Cursor	2026-04-12 19:17:09 +00:00
Colin McDonnell	421607cf97	fix push-to-action: use CLI direct invocation for token acquisition the inline `node -e` + `TOKEN=$(...)` approach broke because `core.getIDToken()` in @actions/core writes `::debug::` and `::add-mask::` to stdout, polluting the captured value. `node cli.ts gha token` uses `core.setOutput()` which writes to the $GITHUB_OUTPUT file instead of stdout. Made-with: Cursor	2026-04-12 00:47:41 +00:00

Author

SHA1

Message

Date

Colin McDonnell

d1e075fa3b

fix npx binary resolution: run in workspace, not action directory

npx was running with cwd set to the action's own directory, which has
package.json with "name": "pullfrog". npm treats the local package as
satisfying the request and skips the registry fetch, then fails to find
the binary (sh: 1: pullfrog: not found). use GITHUB_WORKSPACE instead.

Made-with: Cursor

2026-04-12 19:17:09 +00:00

Colin McDonnell

421607cf97

fix push-to-action: use CLI direct invocation for token acquisition

the inline `node -e` + `TOKEN=$(...)` approach broke because
`core.getIDToken()` in @actions/core writes `::debug::` and
`::add-mask::` to stdout, polluting the captured value.

`node cli.ts gha token` uses `core.setOutput()` which writes to
the $GITHUB_OUTPUT file instead of stdout.

Made-with: Cursor

2026-04-12 00:47:41 +00:00

2 Commits