This report is very old and it looks like a misuse. My guess is the branch
used as a base for the PR (borgbackup/borg:docs-ml) doesn't exist. You
have to either set a tracking branch or use --base to specify the branch.
I would close as invalid if there is no further response.
On Sun, 13 Dec 20
Package: git-hub
Version: 0.9.0-2
Severity: normal
After figuring out the tangle of configuration needed to keep
github-pull from trying to push the branch to the upstream...
(hint:
hub.upstream=borgbackup/borg
hub.forkremote=anarcat
)
... it actually failed to create the PR with what seems
2 matches
Mail list logo
