restack unexpectedly warning that public commits will be rewritten

[mlw0]

I don't understand the warning I'm getting from git restack here:

$ git sl
⋮
◇ ed70352 1h (main) foo
┃
● e4ec321 30m (ᐅ bar) bar message
┃
◯ 9a02732 1s (baz) baz message
┃
◯ 93fb5b9 1s (qux) qux message

$ git restack
You are trying to rewrite 236 public commits, such as: ed70352 foo
It is generally not advised to rewrite public commits, because your
collaborators will have difficulty merging your changes.
Retry with -f/--force-rewrite to proceed anyways.

In this case, I would expect restack to be a no-op, judging by the linear output of git sl.

I get the same warning even when there is work to do. I always have to do git restack <commit> to ensure that the operation does not attempt to touch these hundreds of public commits.

Is there something wrong with the history of my repo? Or my checkout? Perhaps something I've hidden?

[mlw0]

Re: "I get the same warning even when there is work to do" I was able to reproduce that:

$ git sl
⋮
◇ e4ec321 3h (main) foo
┣━┓
┃ ✕ 9a02732 2h (rewritten as fe08a730) bar message
┃ ┃
┃ ◯ 93fb5b9 2h (baz) baz message
┃
● fe08a73 12s (ᐅ bar) bar message
hint: there is 1 abandoned commit in your commit graph
hint: to fix this, run: git restack
hint: disable this hint by running: git config --global branchless.hint.smartlogFixAbandoned false

$ git restack
You are trying to rewrite 237 public commits, such as: e4ec321 foo
It is generally not advised to rewrite public commits, because your
collaborators will have difficulty merging your changes.
Retry with -f/--force-rewrite to proceed anyways.

$ git restack 9a02732
Attempting rebase in-memory...
[1/1] Committed as: 3c29df3 baz message
branchless: processing 1 update: branch baz
branchless: processing 1 rewritten commit
branchless: creating working copy snapshot
branchless: running command: git checkout bar
Switched to branch 'bar'
Your branch is up to date with 'origin/bar.
branchless: processing checkout
In-memory rebase succeeded.
Finished restacking commits.
No abandoned branches to restack.
⋮
◇ e4ec321 3h (main) foo
┃
● fe08a73 32s (ᐅ bar) bar message
┃
◯ 3c29df3 0s (baz) baz message

[arxanas]

Does git restack 'draft()' do what you expect? If so, what version of git-branchless are you running? This may have been fixed in #914.

[mlw0]

I'm afraid I reran git branchless init to get past this error a few weeks ago, and am therefore no longer able to reproduce it in the affected checkout (or a new repo).