-
Notifications
You must be signed in to change notification settings - Fork 287
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
cli: Add prev/next --conflict
, which allows you to jump to the next conflict.
#3248
Conversation
cf04fd0
to
409b105
Compare
d068fc8
to
46c0987
Compare
This is actually ready for review, I just need some help to finish the tests. I am seemingly unable to introduce the conflicts I want in my tests :-/. |
What do you need help with? Did you try searching the tests for "conflict"? Are you looking for something different? |
27ed987
to
63ba6f3
Compare
7ee55c8
to
ce831db
Compare
10ea3dc
to
1ed88b1
Compare
1ed88b1
to
0fcba44
Compare
0fcba44
to
b21081f
Compare
b21081f
to
c2c23b2
Compare
After thinking a bit on during my holiday, I'm fine with either version. I'd like to land this ASAP though, so I can finally spend my owed time to |
64d4856
to
e2a0017
Compare
This allows users to easily filter a commit range by conflicts, which will be needed for `next/prev` further down in the next commit. Users which benefit from it were also migrated.
This allows users to jump to the next conflict in the ancestors or children of the start commit. Continues work on #2126 Co-Authored-By: Noah Mayr <dev@noahmayr.com>
e2a0017
to
02021e9
Compare
Tests are complete, although I need help there.
Checklist
If applicable:
CHANGELOG.md