←back to thread

I see a future in jj

(steveklabnik.com)
291 points steveklabnik | 3 comments | | HN request time: 0.53s | source
Show context
weinzierl ◴[] No.45674580[source]
I think the real news is that some people have started to build what might become something like a "jjhub".

https://ersc.io/

replies(7): >>45674802 #>>45675236 #>>45675335 #>>45675688 #>>45677818 #>>45678591 #>>45678833 #
steveklabnik ◴[] No.45674802[source]
I think 'jjhub' is a decent immediate first approximation, and is often how I've started out talking about it with people. At the same time, we have to offer real value here, as you can already use jj with github (and I have for a long time now), so there's more to it than that. But yes :)
replies(3): >>45675242 #>>45676675 #>>45678269 #
davidkunz ◴[] No.45675242[source]
What I would love:

- Everything locally stored in the repo: PRs, comments, issues, discussions, boards, ... - CLI first - Offline first (+ syncing) - A website for hosting/presentation

replies(2): >>45675308 #>>45675504 #
1. ElectricalUnion ◴[] No.45675504[source]
So you want Fossil?
replies(2): >>45676492 #>>45677093 #
2. arccy ◴[] No.45676492[source]
except fossil decided to never allow changing history, vs jj which makes history rewriting so much easier
3. anotherevan ◴[] No.45677093[source]
When I tried Fossil it had things weirdly separated.

I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.