You don’t have to convert your team to use jj. So there’s nobody to resist but yourself.
For me, writing temporary output to a gitignored tmp directory has been trivial. And I do exploratory coding in a separate branch. Just because it’s part of the repo doesn’t mean it needs to get pushed.
That's one of the workarounds I had in mind. :)
This week I've had to work with CSVs, SQLite databases, and video in... six... different formats. Some goes in the repo, some doesn't.
It seems like my choices are:
- Disable it in the repo's .jj/repo/config.toml.
- Get people that don't like it to turn it off.
- Get people to do their exploratory coding in a gitignored directory.
It feels like any choice I make is going to be met with resistance.