Cleaning up superfluous revisions in jj log
#4965
-
I've been making contributions to someone else's project. I created a fork of their repo, and I have both of the remotes set in my local repo. My problem is that, after a few (~4) contributions, my Raw text representation of `jj log`
What are all those conflicted commits and how are they empty?? And what's the "correct" way to clean them. I can see they show up as part of The way I've been contributing is something like:
Some debugging info:
My entire `jj op log`
Using a default repo |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
See https://martinvonz.github.io/jj/latest/FAQ/#how-do-i-deal-with-divergent-changes-after-the-change-id for some explanation of why they might be divergent. I sent PR #4966 to try to explain why merge commits are often empty.
What happens on the remotes when the PR has been merged? Is the remote configured to delete the branch? If it is, then the next |
Beta Was this translation helpful? Give feedback.
See https://martinvonz.github.io/jj/latest/FAQ/#how-do-i-deal-with-divergent-changes-after-the-change-id for some explanation of why they might be divergent. I sent PR #4966 to try to explain why merge commits are often empty.
What happens on the remotes when the PR has been merged? Is the remote configured to delete the branch? If it is, then the next
jj git fetch
should detect that the branch was deleted, and any commits that are no longer reachable on…