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
git push-to-branch <branches> -r <revision> which would push branches to the remote.
This would behave similarly to jj branch set (possibly with --allow-backwards) and jj git push (although would only push the related branches/revision).
Potential options:
--revision/-r
--allow-backwards/-B
--remote
How it would look
# Start new change
jj fetch
jj new main@origin
# Do changes, commit
jj commit
# Push it up!
jj git push-to-branch my-cool-change -r @-
# Make more changes. Can either be a new commit after, or squashed into previous commit
jj commit / jj squash
# Update the remote branch with our changes (however they were recorded)
jj git push-to-branch my-cool-change -r @-
Open questions
Should this command create local branches or remote-only?
The text was updated successfully, but these errors were encountered:
I'm not a fan of this. Doing VCS operations and pushing them at the same time feels like a large footgun. With branch auto advancing, the "commit, branch set, push" flow is already getting reduced from 3 to 2 steps.
Is your feature request related to a problem? Please describe.
When pushing to a git remote, 2 operations must happen:
jj branch set <branches> -r <revision>
(and optionally create until FR: Upsert branch (update branch or create if it does not exist) #3584 lands)jj git push
Describe the solution you'd like
git push-to-branch <branches> -r <revision>
which would push branches to the remote.This would behave similarly to
jj branch set
(possibly with--allow-backwards
) andjj git push
(although would only push the related branches/revision).Potential options:
--revision
/-r
--allow-backwards
/-B
--remote
How it would look
Open questions
The text was updated successfully, but these errors were encountered: