I was suggested to use sl pr unlink when trying to run sl pr submit when the associated GitHub PR had already been closed. I then attempted that, but it didn't seem to change the sl state at all.
This was on the macOS version installed by brew.
% sl version
Sapling 0.2.20240718-145624+f4e9df48
(see https://sapling-scm.com/ for more information)
This was the latest version available through brew (previously called brew upgrade sapling).
sl, sl pr unlink, sl (on the base commit bcc265a08):
% sl
o 993234c71 15 minutes ago greg
│ xtask: Convert structopt to using clap
│
@ bcc265a08 15 minutes ago greg #13
╭─╯ Update .committemplate to repo
│
o 753ebd9e9 26 minutes ago remote/main
% sl pr unlink
% sl
o 993234c71 15 minutes ago greg
│ xtask: Convert structopt to using clap
│
@ bcc265a08 15 minutes ago greg #13
╭─╯ Update .committemplate to repo
│
o 753ebd9e9 26 minutes ago remote/main
sl pr submit still fails after this with the same error as before and offers the same guidance to use sl pr unlink.
I tried installing sl from brew at --HEAD, but that version is giving me issues:
% sl
unknown python exception%
I was suggested to use
sl pr unlinkwhen trying to runsl pr submitwhen the associated GitHub PR had already been closed. I then attempted that, but it didn't seem to change theslstate at all.This was on the macOS version installed by
brew.This was the latest version available through
brew(previously calledbrew upgrade sapling).sl,sl pr unlink,sl(on the base commitbcc265a08):sl pr submitstill fails after this with the same error as before and offers the same guidance to usesl pr unlink.I tried installing
slfrombrewat--HEAD, but that version is giving me issues: