Skip to content
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

Merged
merged 1 commit into from
May 1, 2024

Conversation

poliorcetics
Copy link
Contributor

@poliorcetics poliorcetics commented Mar 2, 2024

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):

Screenshot 2024-03-30 at 20 34 56

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added tests to cover my changes

I don't know if this deserves a changelog entry ? It's a small polish thing

@poliorcetics poliorcetics added enhancement New feature or request rust polish🪒🐃 Make existing features more convenient and more consistent labels Mar 2, 2024
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch 2 times, most recently from f506365 to 97dae12 Compare March 2, 2024 17:24
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch 3 times, most recently from bb0942d to 69a1ca4 Compare March 8, 2024 00:05
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch 2 times, most recently from d8ad8b1 to 5e796eb Compare March 13, 2024 16:51
cli/src/cli_util.rs Outdated Show resolved Hide resolved
cli/src/commands/status.rs Outdated Show resolved Hide resolved
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch 2 times, most recently from 280336b to 5efaa63 Compare March 30, 2024 19:38
@poliorcetics
Copy link
Contributor Author

I marked all comments as resolved since I changed the implementation a lot: it now searches for the conflicts roots and says to jj new from there, like it does when rebasing already. It means someone doing jj new over the root conflict will still get the message but I think that's okay for a first approach: at this point, the user know what they're doing and they can easily ignore the hint

@poliorcetics poliorcetics requested a review from martinvonz March 31, 2024 02:11
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch from 5efaa63 to cd7b8c2 Compare April 9, 2024 20:23
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch from cd7b8c2 to 7a0b032 Compare April 10, 2024 19:20
@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch 2 times, most recently from bf05957 to 1193c0f Compare May 1, 2024 13:47
@martinvonz
Copy link
Member

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?

@poliorcetics
Copy link
Contributor Author

I forgot to merge it for a long time and now tests are broken, I'm fixing right now

@poliorcetics poliorcetics force-pushed the ab/push-vqytsmpzknyk branch from 1193c0f to 7b8efb4 Compare May 1, 2024 13:49
@poliorcetics poliorcetics enabled auto-merge (rebase) May 1, 2024 13:50
@poliorcetics poliorcetics merged commit 52e494d into main May 1, 2024
16 checks passed
@poliorcetics poliorcetics deleted the ab/push-vqytsmpzknyk branch May 1, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request polish🪒🐃 Make existing features more convenient and more consistent
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FR: Display rebase instructions in status
4 participants