PR "created" but doesn't actually exist
jas88 opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
Nuget
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
Log claims 3 PRs created, none actually appear in repo
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
https://github.com/SMI/RdmpDicom/network/updates/835116513
(Repo is public, Dependabot log seems to need auth though)
At end:
updater | | created | YamlDotNet ( from 15.1.4 to 15.1.6 ) |
updater | | created | HIC.BadMedicine.Dicom ( from 0.0.16 to 0.1.0 ) |
updater | | created | Terminal.Gui ( from 1.16.0 to 1.17.0 ) |
But no such PRs exist, neither open nor closed.
Smallest manifest that reproduces the issue
No response
Update: the job status was later updated to "failed to create PR" with an error POST https://api.github.com/repos/SMI/RdmpDicom/git/trees: 422 - GitRPC::BadObjectState // See: https://docs.github.com/rest/git/trees#create-a-tree
A subsequent run claimed to create the same 3 PRs, but actually succeeded in creating one. Hopefully trying again a few times will eventually create all 3...
This may be a submodules issue; updating the one and only submodule to a version which had no outstanding dependency updates gave a clean Dependabot run afterwards.