Jujutsu support

[Elias-Ainsworth]

Is your feature request related to a problem? Please describe.
This looks like an amazing tool! But the only reason I'm refraining from using it is the lack of jujutsu support.

Describe the solution you'd like
Additional support for the jujutsu vcs that can be toggled in the config file.

Describe alternatives you've considered
The old fashioned method of amending commits.

Additional context

[cococonscious]

This looks nice, I'll take a look for the release after the next one!

[cococonscious]

Could you elaborate a little on what features you want for jujutsu? I haven't used it before but from what I understood, koji could be used for jj describe and jj new, where the former is quite similar to the hook functionality of koji, no? If I'm right, would you be happy with koji --hook doing jj describe and the normal mode doing jj new?

[Elias-Ainsworth]

That looks great, but then again I'm not exactly the most avid jujutsu user, so I apologize for the lack of constructive feedback.

PS. Have you considered packaging koji for nix from within the repository?

[cococonscious]

PS. Have you considered packaging koji for nix from within the repository?

Yes, I'm going to look into packaging koji for various package managers (including nix) as soon as #139 (and maybe #140) have been implemented and released. Please note that the package that's currently in the Nix repository is not managed by me or anyone I'm affiliated with (@ByteSudoer) and is also outdated.

[jkellz-dev]

@Elias-Ainsworth I use koji with JJ with the --stdout flag. So when describing jj describe -m "$(koji --stdout)". Since JJ actively manages the lifecycle of changes, I find only using koji's prompt and formatting to be the most helpful. I don't have a clear understanding of how the workflow would work with a deeper integration.

[jkellz-dev]

Also I alias the command so I'm not typing it all the time either. So YMMV.

After rereading the thread, I think invoking koji should describe by default. That may just be how I work and is clearly a preference. It would be rad if invoking koji a second time pre-populated the defaults with the previous message. Then describing multiple times would be more like editing your working copy.