-
Notifications
You must be signed in to change notification settings - Fork 39
feature: escape action #174
New issue
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
Conversation
Thanks for the PR. I'll review this in a bit. Sorry for the additional trouble, but would you mind using the "self review" commit as a fixup commit for the first, and openening a separate PR for the fix for #170? |
I am doing it. I am curious, why do not you use "squash merge"? |
Well, it's a valid question. I suppose in such an easy and obvious case we could. But generally spoken, the author may have had reasons to create separate commits which should also be visible in commit history after merging. For bigger PRs it could become difficult to distinguish this from mere formatting changes. So with that in mind, personally, I'd rather prefer squashing that in the PR. But it's no more than a personal feeling. I don't know how @gabm feels about this. ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this could do with another cargo fmt
, right? Other than that and the change below, looks good to me.
Should be fine @RobertMueller2 thank you for the review! |
github doesn't let me right now, I'll try again later. |
fixes #172
How
I've reused the action on enter idea.
I've made 3 new actions but we could argue that
early_exit
is enough.Example
Misc
My first attempt was roughly this but it was unconsistent: