mattbrictson / mattbrictson/bundle_update_interactive
Bulk selection for patch level and risk of breaking changes
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 246
- Forks
- 7
- Avg merge
- 15h 31m
- Merged PRs (30d)
- 3
Description
### Use Case
As a **user** I would like to **select all gems**
based on the level of risk it takes to update them.
### For example:
If I only want to update gems which will not break.
In this case a keymap to select all of them would be very helpful.
Contributor guide
No contributing guide indexed for this repository
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 tracing the interactive CLI's current gem-selection flow and how it determines patch-level updates or breaking-change risk. Identify the existing keymap and selection entry points, then define completion as selecting all gems in the requested risk category without changing other selection behavior; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100