You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A pain point for me using jj is the extra typing involved to do the equivalent of "git push" and "git pull". Namely, the manual moving around of bookmarks when pushing and pulling is both error prone and tedious for me, especially when doing it frequently (which I often do). I'm the kind of guy that likes to push every few minutes to the remote repository.
Describe the solution you'd like
My dream solution is to be able to run jj git push without having to first run jj bookmark move. I'd also like to be able to run jj git pull (a command that does not exist at the time of writing) instead of jj git fetch followed by manually creating a merge commit.
Describe alternatives you've considered
Maybe there is a fancy way to write a revset to do this?
Additional context
Nothing.
The text was updated successfully, but these errors were encountered:
This will be possible in a native future or if you already work in g3. For your jj git pull command there's #1039. And there are the proposed Topics (#3402) for a simpler topological branching model.
Is your feature request related to a problem? Please describe.
A pain point for me using
jj
is the extra typing involved to do the equivalent of "git push" and "git pull". Namely, the manual moving around of bookmarks when pushing and pulling is both error prone and tedious for me, especially when doing it frequently (which I often do). I'm the kind of guy that likes to push every few minutes to the remote repository.Describe the solution you'd like
My dream solution is to be able to run
jj git push
without having to first runjj bookmark move
. I'd also like to be able to runjj git pull
(a command that does not exist at the time of writing) instead ofjj git fetch
followed by manually creating a merge commit.Describe alternatives you've considered
Maybe there is a fancy way to write a revset to do this?
Additional context
Nothing.
The text was updated successfully, but these errors were encountered: