dependabot / dependabot/dependabot-core
@dependabot recreate misleads users
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 1.5k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 151
Description
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
all
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
This is not the behavior experienced. The PR is not "overwritten", but instead closed and a new one opened. This is related to the bizarre behaviour seen in: https://github.com/dependabot/dependabot-core/issues/7894
https://github.com/autobrr/autobrr/pull/1057#issuecomment-1693857707
creates:
https://github.com/autobrr/autobrr/pull/1059
Dependabot seems to always do the wrong thing here.
Again, I'm happy to spend 15 minutes with PM around this if desired (and was offered through maintainers).
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Dependabot's handling of the @dependabot recreate command and compare the behavior described in pull requests 1057 and 1059 with related issue 7894. Review the referenced .github/dependabot.yml for context. Done means the command's behavior and user-facing explanation agree, with coverage for the recreate flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ruby
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100