-
Notifications
You must be signed in to change notification settings - Fork 353
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: status: when current change has conflicts, display instructions to resolve them #3190
Conversation
f506365
to
97dae12
Compare
bb0942d
to
69a1ca4
Compare
d8ad8b1
to
5e796eb
Compare
280336b
to
5efaa63
Compare
I marked all comments as resolved since I changed the implementation a lot: it now searches for the conflicts roots and says to |
5efaa63
to
cd7b8c2
Compare
cd7b8c2
to
7a0b032
Compare
bf05957
to
1193c0f
Compare
Can you remind me of the status of this PR? I see that I approved it a long time ago. Why have you not merged it yet (I don't mean that in an accusatory way)? Was there some discussion here or on Discord that I've forgotten? |
I forgot to merge it for a long time and now tests are broken, I'm fixing right now |
1193c0f
to
7b8efb4
Compare
Fixes #3108
Example output (which takes into account my own jj config and PWD so it's a little wonkier than the test, the screen is to show colors):
Checklist
If applicable:
CHANGELOG.md
I don't know if this deserves a changelog entry ? It's a small polish thing