Skip to content

fix: make workflow stop not-found message explicit + add npm test script#301

Open
bart-btom-oss wants to merge 1 commit intosnarktank:mainfrom
bart-btom-oss:feat/bart-code-pilot
Open

fix: make workflow stop not-found message explicit + add npm test script#301
bart-btom-oss wants to merge 1 commit intosnarktank:mainfrom
bart-btom-oss:feat/bart-code-pilot

Conversation

@bart-btom-oss
Copy link

@bart-btom-oss bart-btom-oss commented Mar 9, 2026

Summary

  • ensure not-found responses for workflow status/stop always include the user query (even when there are zero runs)
  • add npm test script to standardize local/CI validation (build + Node test runner)

Why

  • baseline tests exposed a failing expectation: non-existent run message omitted the queried id when run history was empty
  • repository had tests but no package test script

Validation

  • npm ci
  • npm run build
  • npm test

@vercel
Copy link

vercel bot commented Mar 9, 2026

@btommm is attempting to deploy a commit to the Ryan Team on Vercel.

A member of the Team first needs to authorize it.

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.

2 participants