Commits


add -c option to 'got ref' which now expects just one argument after options


prevent commits from being listed more than once in a histedit script While merging a commit multiple times during a histedit operation could potentially make sense in some corner case, a commit appearing more than once in the script is more likely to happen accidentally. If desired, the same effect can still be achieved by running multiple histedit operations, or by using 'got cherrypick' while the histedit operation is paused for arbitrary editing.


fix histedit 'rebase commit ID mismatch' error when splitting a commit Commit IDs on histedit's temporary branch can change arbitrarily because the user may create new commits on this branch while editing past commits. So there is no point in trying to verify these IDs like we do during rebase. Add a test case which demonstrates the problem.


fix 'last commit cannot be folded' check with reordered commits


fix and test interaction of rebase/histedit -c and 'got stage'


forbid editing the history of branches outside of "refs/heads"


add another histedit test for path prefix behaviour


rename a histedit test


remove some unused variables from histedit tests


check committed diffs in some histedit tests


add histedit path prefix test


histedit: make folding work across dropped commits


initial 'got histedit' implementation