I'm not sure how I got here, because I've been using spr without issue so far (albeit only for a few days). But earlier, I went to update an upstream PR with spr diff, and instead of the expected update, spr behaved like it was seeing this commit for the first time and created a whole new PR for it.
I've tried all sorts of things, like closing all the upstream spr/ branches, pruning the remotes, re-running spr init, generating a new PAT, cloning the remote repo again. All with no success. Here's a screenshot of the type of behavior I'm seeing:
Update: The misbehavior is specific to the repository used in the screenshot...
Update 2: I've found that pointing spr in the same repository to a different upstream (a fresh GitHub repository with a different name in a different org) gets it working normally. So it looks like the problem might be related to the original upstream repository's settings.
Update 3: On a hunch, I removed the period, ., from the repository name and suddenly things are working again!
I'm not sure how I got here, because I've been using
sprwithout issue so far (albeit only for a few days). But earlier, I went to update an upstream PR withspr diff, and instead of the expected update,sprbehaved like it was seeing this commit for the first time and created a whole new PR for it.I've tried all sorts of things, like closing all the upstream
spr/branches, pruning the remotes, re-runningspr init, generating a new PAT, cloning the remote repo again. All with no success. Here's a screenshot of the type of behavior I'm seeing:Update: The misbehavior is specific to the repository used in the screenshot...
Update 2: I've found that pointing
sprin the same repository to a different upstream (a fresh GitHub repository with a different name in a different org) gets it working normally. So it looks like the problem might be related to the original upstream repository's settings.Update 3: On a hunch, I removed the period,
., from the repository name and suddenly things are working again!