Merged
Conversation
- Compile commits in forward order, starting from the oldest one - Check out the branch itself when done instead of the head commit by hash
kcgen
approved these changes
Aug 15, 2023
Member
kcgen
left a comment
There was a problem hiding this comment.
Looks good, and nice improvement!
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☝🏻 Should be pretty straighforward. Creating this script was a great idea @kcgen and it's super handy—I just wished it worked a bit differently... now it does 😎
Feel feel to disagree with any of this; I just find this slightly tweaked mode of operation more useful. Especially checking out the head by commit hash vs the actual branch name at the end trips me up every single time 😅 I would expect the script to restore the "Git state" exactly to where it was started from.