-
Notifications
You must be signed in to change notification settings - Fork 33
make squash command add some visual feedback that the squash is running #574
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
base: master
Are you sure you want to change the base?
Conversation
Current Aviator status
This pull request is currently open (not queued). How to mergeTo merge this PR, comment
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
0b02e81 to
ab009af
Compare
ab009af to
d00ac76
Compare
✅ FlexReview StatusCommon Owner:
Review SLO: |
|
@Brookke making some small changes to the squash command, would love your feedback as well if you have any thoughts. |
|
Looks good! However, realised I have a bug in this and the current prod version where it squashes one too many commits 🤦🏻 I probably missed this in my PR due to my too simple testing setup. @tulioz |
| colors.Success(fmt.Sprintf("Successfully squashed %d commits", len(commitIDs))), | ||
| "\n", | ||
| ) | ||
| fmt.Fprint(os.Stderr, amendMessage, "\n\n") |
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 wonder if we should still include the amendMessage? it gives a nice summary of what the squash did
No description provided.