mattbrictson / mattbrictson/bundle_update_interactive
> wisper's executable "console" conflicts with graphql-rails_logger
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 246
- Forks
- 7
- Avg merge
- 15h 31m
- Merged PRs (30d)
- 3
Description
```sh
> gem install bundle_update_interactive
wisper's executable "console" conflicts with graphql-rails_logger
Overwrite the executable? [yN]
```
This happens because the files in `bin` are automatically included in the bundled gem. I don't remember from the top of my head, but there's a way to exclude `bin` directory so that `console` and similar are no longer conflicting.
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 inspecting how the gem packages the bin directory and reproduce the conflict with `gem install bundle_update_interactive`. Check the generated executables and packaging configuration; done means installing the gem no longer prompts to overwrite wisper's `console` executable or conflicts with graphql-rails_logger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100