Skip to content

v0.1.8

Latest

Choose a tag to compare

@github-actions github-actions released this 24 Oct 17:33
Immutable release. Only release title and notes can be modified.

jj-stack 0.1.8 lets you stack your work on any open PR, including a colleague's, and merge now waits for required checks instead of failing while they run.

Highlights

  • submit --base <parent-change-id> --base-pr <number-or-url> <head-change-id> builds a stack on an existing open PR, including one created outside jj-stack. The parent PR is never pushed, linked, or changed; its current head must match your local parent. See Build on someone else's PR.
  • merge waits for the selected PRs' required checks to pass before asking GitHub to merge, and stops with a link to the results if one fails. Press Ctrl-C during this wait to stop without requesting a merge. --no-wait skips the wait.
  • jj-stack can be installed or run with Nix: nix run github:bos/jj-stack -- --help. See the README for adding it to a flake configuration.
  • jj 0.46.0 is now tested alongside the minimum supported version, 0.45.1.

Fixes

  • submit, sync, and merge no longer look hung when ssh asks for a key passphrase: the progress spinner used to erase the prompt.
  • If someone else's branch was built on an earlier version of your change, jj shows the change as divergent. submit, sync, and view no longer refuse to work on it; they use your local copy and leave theirs alone.
  • After you close a whole stack on GitHub, cleanup removes it in one run. It previously told you to run unstack first, and then needed one run per PR to delete its branches. sync --all benefits too.
  • A power loss or crash while jj-stack saves its PR links can no longer leave an empty tracking file that blocks every command until you relink your PRs.
  • With jj 0.46.0, when a merged change is still checked out in a workspace whose directory was deleted, sync suggests jj workspace forget instead of a command in the missing directory.

Automation

  • The divergent change status now means more than one mutable commit exists for the change; immutable copies no longer count.

Full changelog