-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Analyze commits only from the defined directory #109
Comments
+1 for this. I have a project that contains frontend code (html/javascript) and backend code (python). Frontend code and node_modules also contains python files. I only want to analyze my backend code, but there is no option to do that. wily will always analyze the whole git repo, no matter what. It would be very good to have an option or setting for narrowing down to given subdirectories. |
@suola I applied your patch locally leading to 14 failing tests. Currently, I do not have the time to investigate it further and check whether the patch makes sense, is doable and how to test it afterwards. However, I see the need for analysing only a single directory and would be happy to see this feature. If you like and have the time, submit a PR and @ mention me so I can have a look at it. |
Idea: Print only the commits where at least one metric does not print |
This is trivial to do, and happens in #187 (from a CLI option) but it also omits lines where no changes happened. Should I make it always omit commits where all metrics print |
Assume I have a project
I want to analyze only
foo/baz
and I run> wily build foo/baz
Now this goes through all the commits in the git history. Would it be possible for it to go through only the commits in the
foo/baz
directory?I was able to make it work for myself with the following patch, but I don't know whether this would be the right way to do such a change.
The text was updated successfully, but these errors were encountered: