make sure dependabot knows how to handle the new branches
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 100
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 30
Description
I ran into https://github.com/openedx/paragon/pull/3338#issuecomment-2539255363 when trying to get dependabot to recreate a PR the other day.
I want to make sure we don't accidentally tell dependabot to ignore versions by closing PRs. I also want to make sure dependabot is PRing to all the branches it needs to.
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 by reading the linked pull request comment at https://github.com/openedx/paragon/pull/3338#issuecomment-2539255363 and reviewing the repository's Dependabot and branch configuration. Determine which branches should receive dependency pull requests and how closing a pull request affects version handling; done means the configuration and behavior cover all required branches without unintentionally ignoring versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100