chore: Added a little dev script to help contributors#4793
chore: Added a little dev script to help contributors#4793jamescrosswell merged 12 commits intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4793 +/- ##
=======================================
Coverage 74.01% 74.01%
=======================================
Files 499 499
Lines 18065 18065
Branches 3518 3518
=======================================
Hits 13370 13370
Misses 3836 3836
Partials 859 859 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
…bleAsync Two issues in IsCommandAvailableAsync: - On Windows, the method unconditionally returned true without checking whether the command actually exists. Switch to 'where.exe' (the Windows equivalent of 'which') so availability is actually verified. - On Unix, stdout/stderr were not redirected, causing 'which' output (e.g. /usr/bin/sudo) to leak to the user's console. Redirect both streams and consume them before waiting for exit to suppress the noise and avoid a pipe-buffer deadlock. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 participants
This emulates various commands that I have in my .zshrc file that I use frequently when working with the repo. Over time we could potentially expand on these (for example, it would be great to add one that ran various regexes on the logs output by integration/device tests, to identify errors/problems... currently we have to do this manually).
#skip-changelog