Finally rebased some branches for #BitRitter (thanks jujutsu) to get translations and XDG spec working.
When i have inserted all strings, i will tag another release.

Would have given me headaches with plain git.

Nextvon the list is (still) flatpak bundling, then 2 minor issues.

#JujutsuVCS #BitWarden

Jujutsu v0.41.0
https://github.com/jj-vcs/jj/releases/tag/v0.41.0

Release highlights:
* `jj fix` now supports formatting specific line ranges (allowing you to format
only modified lines); see the configuration manual and notes below for more.
* The new global flag `--no-integrate-operation` will let you run a command without impacting the repo state or the working copy, which is useful when automated tools may create snapshots in the background.

#jj #jjVCS #jujutsu #jujutsuVCS

Jujutsu v0.39.0
https://github.com/jj-vcs/jj/releases/tag/v0.39.0

Release highlights:
* `jj arrange` command brings up a TUI where you can reorder and abandon revisions.
* `jj bookmark advance` automatically moves bookmarks forward to a target revision (defaults to @) using customization points revsets.bookmark-advance-from and revsets.bookmark-advance-to. It is heavily inspired by the longstanding community alias jj tug.

#jj #jjVCS #jujutsu #jujutsuVCS

Jujutsu is just nice to work with.

I do not often have to do complex rebasing/merging/squashing work, but i can always undo. Don't worry chfkch, it will be okay.

#JujutsuVCS #JJ

Jujutsu PSA:

Running `jj st` ¹ may change the state of your repository, even though it looks like it should be a read-only command. Consider the following steps:

1. Create a file xyz in your repository
2. Run `jj st`
3. Add xyz to .gitignore

If you omit step 2., the outcome changes. Namely, `jj st` causes file xyz to be tracked, and it keeps being tracked even after you have added it to .gitignore. If you don't run `jj st`, xyz is ignored, as you would probably expect.

Caused me a headache today 😅

¹ And probably other commands which you would expect to be read-only

#jj #jujutsu #jujutsuVCS

Jujutsu v0.38.0
https://github.com/jj-vcs/jj/releases/tag/v0.38.0

Release highlights:
- Per-repo and per-workspace config is now stored outside the repo, for security reasons. This is not a breaking change because legacy repos are automatically migrated to this new format. `.jj/repo/config.toml` and `.jj/workspace-config.toml` should no longer be used.

#jj #jjVCS #jujutsu #jujutsuVCS

Jujutsu v0.37.0
https://github.com/jj-vcs/jj/releases/tag/v0.37.0

Release highlights:
- A new syntax for referring to hidden and divergent change IDs is available: xyz/n where n is a number. For instance, xyz/0 refers to the latest version of xyz, while xyz/1 refers to the previous version of xyz. This allows you to perform actions like jj restore --from xyz/1 --to xyz to restore xyz to its previous contents, if you made a mistake.

#jj #jjVCS #jujutsu #jujutsuVCS

Jujutsu v0.36.0
https://github.com/jj-vcs/jj/releases/tag/v0.36.0

Release highlights:
- The documentation has moved from https://jj-vcs.github.io/jj/ to
https://docs.jj-vcs.dev/.
- It is now safe to
continuously run e.g. jj log without --ignore-working-copy in one
terminal while you're running other commands in another terminal.
- jj now ignores $PAGER set in the environment and uses less -FRX on most
platforms (:builtin on Windows).

#jj #jjVCS #jujutsu #jujutsuVCS

Tiens, j’avais raté, Korben a écrit un petit article de présentation de Jujutsu.

Il a bien raison de dire que « vos collègues peuvent continuer avec Git classique sans même savoir que vous utilisez jj ».

Par contre, la référence à Google dès le titre peut rebuter. À la base c’est un projet perso de Martin von Zweigbergk, qui est maintenant payé à plein temps par Google pour développer son idée.

https://korben.info/jj-jujutsu-version-control-alternative.html

#Jujutsu #JujutsuVCS #Git #Korben