We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exit 0
In another project, I use run-pty --auto-exit to run 5 checks.
run-pty --auto-exit
Locally, everything (so far) works perfectly.
But in GitHub Actions, some commands can sometimes exit early with code 0, causing lint errors and suchlike not to be caught in CI.
I need to dig deeper into this. First thing is to try to reproduce it in this repo I think, that’ll make debugging much easier.
The text was updated successfully, but these errors were encountered:
This seems to be a bug in node-pty (or potentially Node.js 18.18+ and 20.3+): microsoft/node-pty#630
Sorry, something went wrong.
Workaround released in v5.0.0.
No branches or pull requests
In another project, I use
run-pty --auto-exit
to run 5 checks.Locally, everything (so far) works perfectly.
But in GitHub Actions, some commands can sometimes exit early with code 0, causing lint errors and suchlike not to be caught in CI.
I need to dig deeper into this. First thing is to try to reproduce it in this repo I think, that’ll make debugging much easier.
The text was updated successfully, but these errors were encountered: