Skip to content

Conversation

@andrewbranch
Copy link
Collaborator

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Nov 3, 2023

🦋 Changeset detected

Latest commit: 5dba9a9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@arethetypeswrong/cli Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Comment on lines -32 to -33
"[email protected]", // Invalid gzip data
"[email protected]", // Invalid gzip data
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These were fixed by #103

@jakebailey
Copy link
Contributor

jakebailey commented Nov 3, 2023

Hello drive by reviewer here; I would suggest choosing something < 125; 126 and 127 are special codes in the shells (which I learned from https://git-scm.com/docs/git-bisect#_bisect_run), with 125 being bisect's "untestable".

@jakebailey
Copy link
Contributor

on second thought, it's 125 that's special, 126/127 are just errors to bisect, so, ignore me have a nice day

@andrewbranch
Copy link
Collaborator Author

I chose 127 because I feel like I’ve definitely seen it for errors, but the reason I’ve seen it is probably that it is special to shells https://tldp.org/LDP/abs/html/exitcodes.html. I’ll pick something else 😄

@andrewbranch andrewbranch changed the title Use exit code 127 for errors, 1 for failures Use exit code 3 for errors, 1 for failures Nov 3, 2023
@andrewbranch andrewbranch merged commit 3fae6b0 into main Nov 3, 2023
@andrewbranch andrewbranch deleted the error-exit-code branch November 3, 2023 23:02
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.

3 participants