Issue accepting arguments for gh run #416

Activity

1. aeppling

   added

   bugSomething isn't workingSomething isn't working

   on Mar 8, 2026
2. saimonmoore commented on Mar 8, 2026

   

   saimonmoore

   on Mar 8, 2026

   Author

   More actions

   Nice. Thanks for the quick fix!
3. pszymkowiak

   added 3 commits that reference this issue on Mar 10, 2026

   fix: gh run view --job flag loses its value (#416)

   ...

   218b97b

   fix: gh run view --job flag loses its value (#416) (#477)

   ...

   3f37f5a

   chore: merge develop into master (#499)

   ...

   d0396da
4. pszymkowiak commented on Mar 12, 2026

   

   pszymkowiak

   on Mar 12, 2026

   Collaborator

   More actions

   Fixed in v0.29.0 — gh run view --job <id> now preserves the flag value correctly.
5. pszymkowiak

   added

   effort-smallQuelques heures, 1 fichierQuelques heures, 1 fichier

   filter-qualityFilter produces incorrect/truncated signalFilter produces incorrect/truncated signal

   good first issueGood for newcomersGood for newcomers

   priority:medium

   on Mar 20, 2026
6. pszymkowiak commented on Mar 20, 2026

   

   pszymkowiak

   on Mar 20, 2026

   Collaborator

   More actions

   wshm · Automated triage by AI

   🔍 Automated Triage

   🐛 Category	bug
   🟡 Priority	medium
   🎯 Confidence	88%

   Summary

   gh run view passthrough args (e.g. --job) are not correctly forwarded, causing flag-parsing errors; PR #419 already in progress.

   💡 This looks like a simple fix that could be auto-resolved. Use /wshm fix to attempt it.

   ---

   Triaged automatically by wshm · This is an automated analysis, not a human review.
7. aeppling

   closed this as completedon Apr 6, 2026
8. thehoff

   added 2 commits that reference this issue on May 14, 2026

   fix: gh run view --job flag loses its value (rtk-ai#416) (rtk-ai#477)

   ...

   ac8e660

   chore: merge develop into master (rtk-ai#499)

   ...

   252e621