v0.7.0 #827
Replies: 1 comment 3 replies
-
|
Looks great! I'm a bit confused by #730, though. Can you elaborate on why that is the new default? I commonly reword the head commit, but almost never reword the entire stack at once |
Beta Was this translation helpful? Give feedback.
-
|
It that was discussed briefly on Discord, I think. As I recall, it's easier for those of us that prefer to reword HEAD to add a single That being said, I've got a local change that allows configuration of the default revset for |
Beta Was this translation helpful? Give feedback.
-
|
Yep, you can also see the commit message at ed3f1f0. Of course, you can manually alias |
Beta Was this translation helpful? Give feedback.
-
|
Ooh neat. You're definitely right about how making that default will introduce people to that feature; probably wouldn't have discovered it otherwise 😊. Makes sense to me Re commit message: I wonder if there's a way to make the description of work more readily accessible. I clicked the PR link in your description above and saw an empty description, so assumed there wasn't one |
Beta Was this translation helpful? Give feedback.
-
To install or update
git-branchless, run the following:If you haven't already taken the user survey, please consider doing so!
Release highlights
git testto help working with patch stacks. See the postgit test fix,git test run --searchfor details and demos.git testnow implements afixsubcommand to run formatters/linters/etc. on each commit and apply their changes.git test runnow implements linear, reverse-linear, and binary search.git reword,git switch, andgit record; see below.Changelog
Added
git amend --reparentoption #646)git amendnow supports a--reparentoption to adjust the contents of a commit while keeping the children commits exactly the same.git branchless initwill now populate the internal commit graph structure, rather than waiting for the first invocation of agit branchlesssubcommand.-I/--insertflag #725) Addedsiblings()revset function to determine the siblings of a given commit.-I/--insertflag #725) Added an-I/--insertoption togit recordto insert the new commit before all of the current commit's children.--detachflag togit branchless switch#763) Added a-d/--detachoption togit branchless switchto switch to a commit without checking out any associated branches (as might happen due to thebranchless.navigation.autoSwitchBranchesconfiguration variable), or to switch to a branch without checking it out.git test fixsubcommand #766) Added agit test fixsubcommand to apply formatters/linters/etc. to a set of commits.git test run --searchoption #777) Added the--searchoption togit test runto search a set of commits using linear or binary search for the first commit(s) which cause the tests to fail.git test run --searchoption #777)git test runnow aborts the overall test run when a test returns exit code127.git test run --searchoption #777)git test runnow sets theBRANCHLESS_TEST_COMMITandBRANCHLESS_TEST_COMMANDenvironment variables when running the test command.tests.passed,tests.failed,tests.fixablerevsets #785) Addedtests.passed(),tests.failed(), andtests.fixable()revset functions, whose results are populated bygit test.--reverseoption togit smartlog.Changed
stack() | @#730) BREAKING: The default revset forgit rewordis nowstack() | @instead of@, to simultaneously reword all commits in the current stack.--detachflag togit branchless switch#763) BREAKING:git branchless switchno longer implicitly opens the interactive commit selector when no target is provided. You must explicitly pass-i/--interactiveto do so.--createinstead of--branch#801) BREAKING: The parameter togit recordhas been renamed from-b/--branchto-c/--create.git submitnow colorizes the names of the affected branches.--detachflag togit branchless switch#763) Runninggit branchless switchwith no arguments will switch to the branch associate with the current commit, if there is exactly one such branch and thebranchless.navigation.autoSwitchBranchesconfiguration variable is set totrue.git rewordis now of the formCOMMIT_EDITMSG-*.txt, which your editor can use to detect it as a Git commit message file.git testprogress and output has been changed.Fixed
git amend --reparentoption #646) Adjusted messaging during merge conflicts withgit move --in-memoryto be more accurate.git test runnow recovers from previously-failed tests instead of failing indefinitely in future runs.git submitno longer force-pushes the current branch in the circumstance that all branches are currently up-to-date.git amendnow respects the--mergeoption.git rewordnow supports invoking editors with spaces in their names.post-applypatchhook #724)git branchless initnow installs apost-applypatchhook, for users ofgit am.git branchless initnow respects a leading~in thecore.hooksPathconfiguration variable.git sync, etc. now correctly clean up remote branch information for branches which have been merged upstream. Previously, the remote branch information would be left behind, which would cause future branches with the same names to incorrectly become associated with the old remote branch.git syncwill no longer attempt to resolve merge conflicts unless you pass--merge. Previously, this could happen when attempting to sync merge commits.New Contributors
Thanks to the following first-time contributors!
If you're interested in contributing, check out the Developer Guide in the Wiki, or post in the Discussions or Discord server to ask any questions.
This discussion was created from the release v0.7.0.
Beta Was this translation helpful? Give feedback.
All reactions