← Back to context Comment by mateusz834 18 hours ago or use jj and stop worrying about gitjj split --interactive {ref} 5 comments mateusz834 Reply BeetleB 18 hours ago You don't need --interactive. It is interactive by default. cleaning 14 hours ago This. Can't imagine going back to git after getting comfortable with jj, it's excellent. pixl97 18 hours ago Ah yes, I'll just pass that over to the compliance team and wait a few months for a denial. BeetleB 18 hours ago You need compliance to install jj? nomel 13 hours ago jj uses git as a backend, even though it's not a git frontend. You can use it in a "colocated" mode, with an existing git clone, alongside your normal git tools. Either way, nobody will know that you're using jj except you.
cleaning 14 hours ago This. Can't imagine going back to git after getting comfortable with jj, it's excellent.
pixl97 18 hours ago Ah yes, I'll just pass that over to the compliance team and wait a few months for a denial. BeetleB 18 hours ago You need compliance to install jj? nomel 13 hours ago jj uses git as a backend, even though it's not a git frontend. You can use it in a "colocated" mode, with an existing git clone, alongside your normal git tools. Either way, nobody will know that you're using jj except you.
nomel 13 hours ago jj uses git as a backend, even though it's not a git frontend. You can use it in a "colocated" mode, with an existing git clone, alongside your normal git tools. Either way, nobody will know that you're using jj except you.
You don't need --interactive. It is interactive by default.
This. Can't imagine going back to git after getting comfortable with jj, it's excellent.
Ah yes, I'll just pass that over to the compliance team and wait a few months for a denial.
You need compliance to install jj?
jj uses git as a backend, even though it's not a git frontend. You can use it in a "colocated" mode, with an existing git clone, alongside your normal git tools. Either way, nobody will know that you're using jj except you.