ok/jj
1
0
Fork 0
forked from mirrors/jj
Code Pull requests Activity
jj/CHANGELOG.md
Martin von Zweigbergk 197f669976 cli: fix git-colocated working copy on Windows 
This patch adds a very simple e2e test of having a working copy shared
with Git. The test initially failed on Windows. The symptom was that
the "master" branch did not get updated when we create a commit using
`jj`. That suggested that we didn't correctly detect that the working
copy was shared. After a lot of troubleshooting, I think I mostly
understand what we going on here (thanks to @arxanas for suggesting
https://github.com/mxschmitt/action-tmate). The path we get from
`git2::Repository::workdir()` seems to not be canonicalized in the
same way as `std::fs::canonicalize()` canonicalizes. Specifically, it
does not have the "\\?\" prefix we get from that function. I suppose
that's because libgit2 is a C library and canonicalizes the path using
some other system call.
2022-03-30 22:09:55 -07:00

2.3 KiB
Raw Blame History

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Breaking changes

  • Dropped support for config in ~/.jjconfig. Your configuration is now read from <config dir>/jj/config.toml, where <config dir> is ${XDG_CONFIG_HOME} or ~/.config/ on Linux, ~/Library/Application Support/ on macOS, and ~\AppData\Roaming\ on Windows.

New features

  • You can now set an environment variable called $JJ_CONFIG to a path to a config file. That will then be read instead of your regular config file. This is mostly intended for testing and scripts.

  • The standard $NO_COLOR environment variable is now respected.

  • jj new now lets you specify a description with --message/-m.

  • When you check out a commit, the old commit no longer automatically gets abandoned if it's empty and has descendants, it only gets abandoned if it's empty and does not have descendants.

  • (#111) When undoing an earlier operation, any new commits on top of commits from the undone operation will be rebased away. For example, let's say you rebase commit A so it becomes a new commit A', and then you create commit B on top of A'. If you now undo the rebase operation, commit B will be rebased to be on top of A instead. The same logic is used if the repo was modified by concurrent operations (so if one operation added B on top of A, and one operation rebased A as A', then B would be automatically rebased on top of A'). See #111 for more examples.

  • jj log now accepts -p/--patch option.

Fixed bugs

  • When sharing the working copy with a Git repo, the automatic importing and exporting (sometimes?) didn't happen on Windows.

[0.3.3] - 2022-03-16

No changes, only trying to get the automated build to work.

[0.3.2] - 2022-03-16

No changes, only trying to get the automated build to work.

[0.3.1] - 2022-03-13

Fixed bugs

  • (#131) Fixed crash when core.excludesFile pointed to non-existent file, and made leading ~/ in that config expand to $HOME/

[0.3.0] - 2022-03-12

Last release before this changelog started.