Alexandre Barret

Using = in the command breaks the command recognition

1

This is really specific problem that shouldn't cause a problem right now. When calling `retest 'rake test ='` the output is: ```bash Setup identified: [RAKE]. Using command: 'bundle exec rake...

A change on a file named `rspec.rb` will try to run the test command with `rspec.rb` file which doesn't have tests and therefore doesn't output anything even though the change...

## Use Case Repository files sometimes share the same name and is difficult to assess. For some use cases, ex: updating a factory file, retest tries to find a matching...

Investigate Hanami 2 (alpha version)

2

Retest should work with Hanami 2. This issues investigates whether the file structure of Hanami 2 is different than Hanami 1

I wonder if we can open retest to use different watching system like [fswatch](https://github.com/emcrisostomo/fswatch) Like an external pipeline We would still use Listen as the default but then open retest...

When updating the file `test_options.rb` I expect retest to select `test_options_test.rb` and not return the file `test_options.rb`

### Describe the problem I'm looking to define options with arguments that can take a command to run in a process. Something like this `my-cli 'rake TEST='` arguments using `=`...

Allow arguments to be hardcoded strings with - and = characters

2

### Describe the change This pull request allows `:argument` option to be a hardcoded string representing a command that can contain args and env variables. **Note: Please advise if there...

Misidentified Rails/Rake setup

1

Retest thinks we're dealing with a rails repository when it is, in fact, a rake setup (via bundler): https://github.com/AlexB52/uni_rails **workaround:** Specifying `--rake` does the trick for now. retest --notify --all...