3 ms·
For every feature we usually have two developers working on it, one frontend and one backend, working on the same feature branch. Would Jujitsu cause a problem
by ashenke 2y ago
For every feature we usually have two developers working on it, one frontend and one backend, working on the same feature branch.
Would Jujitsu cause a problem in this context?
- stouset 2y agoI haven't used this workflow personally, but it should be fine. `jj git push` does an equivalent to `--force-with-lease`, so if there are remote commits that are later than what your current bookmark points to, it won't overwrite them. You can `jj git fetch`, it'll update your bookmark, and you can choose to put your new commits onto the updated sequence of commits wherever they belong.
- steveklabnik 2y agoJust to be clear, as with git, you don’t have to rebase. It’s just that doing so is nicer in jj. But if rewriting commits on a shared branch becomes onerous, don’t do that!