-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running command against changed file #76
Comments
Hi @nickhammond Thanks for the feedback and glad you enjoy retest. Having a I'll definitely consider this for the next release but I can't promise a time frame. |
Hello @nickhammond I have release v1.5.0 which allows you to do what you want. Based on your example I would recommend using
instead of
For example, if we have a A change on
A change on
Let me know if this works as expected :) |
This is great!! I'll give this a go tomorrow and let ya know. |
@AlexB52 Thanks for making this change! Only feedback I have would be to update the "Files Selected" labels to match the placeholders, swap
|
@AlexB52 Having
|
Awesome thanks @nickhammond |
Hey @AlexB52! Really enjoying retest, really lightweight and simple.
I wanted to ping you to see if you had anything in mind or if this is something you have a workflow for. I'd like to run the test like you normally would but then also run rubocop against the changed file as well as the test file.
Something like this:
retest 'bin/rails test <test> && bundle exec rubocop <test> <changed>'
I noticed you just gsub
<test>
from the commandsystem command.gsub('<test>', cached_test_file)
but I think by the time it gets to the runner retest has already detected which spec|test file to use. The rubocop command will take as many files as you throw at it so they can just be listed one after another too.The text was updated successfully, but these errors were encountered: