mattbrictson / mattbrictson/bundleup
feature: run tests and commit after changing any gem version
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 193
- Forks
- 6
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Great project! I believe this could soon be integrated into bundler itself. Wait and see!
I've tested [bundle-auto-update](https://github.com/pcreux/bundler-auto-update/) and quite enjoyed the automated version increment -> test -> commit, but didn't have many gems to update, and since the project isn't maintained anymore I didn't want to rely on it too much.
I'd love to see this tool use the same patch/minor/major -> test -> commit workflow.
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
The issue does not name any files, tests, or entry points. Start by tracing the current gem-version update workflow in the CLI, then determine how patch, minor, and major changes should trigger testing and commits; done means the complete workflow is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100