-
-
Notifications
You must be signed in to change notification settings - Fork 724
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
Support for dotCover configuration file #1401
Comments
@matkoch this sounds like a very useful addition. Are you interested in sending a PR to implement this? |
Quickly checking, the settings param should be added to the abstract DotCoverSettings class and make it available to all DotCover aliases. If @matkoch is not in a position to send a PR, I could send one when I have time (beginning of January).. |
Did anyone do anything with this? I'm guessing not as I can't see it. |
@B3nCr no, not that I am aware of. We would be happy to accept a PR if this is something you are interested in seeing getting added. |
Support for DotCover configuration file added - fixes cake-build#1401
Support for DotCover configuration file added - fixes cake-build#1401
I already added PR |
Support for DotCover configuration file added - fixes cake-build#1401
Support for DotCover configuration file added - fixes cake-build#1401
This would be great to have, is there any news on merging the PR? |
@asci13 Looks like issuer closed the PR #2108, and a new one hasn't been opened. Unsure if it's up for grabs or if @AdaskoTheBeAsT is planning to open a new PR. |
@devlead the source branch is still there, I "think" it just needs another rebase. I was actually just away to look into it... Will report back on what I find. |
Doh! Looks like @AdaskoTheBeAsT hasn't allowed pushing back to his repository. So even though I have rebased the changes onto the latest develop branch, I can't push them back to his repo. I could rebase/merge directly, but we would lose the CI checks prior to merging 😢 |
Permission disappeared when PR closed, unfortunately GitHub won't allow you to reopen a PR , you could push branch to your personal repo and open new PR, original issuer would still get attribution for the commit. |
@devlead interesting idea. I will see what I can do over lunch time. |
Hi, sorry i am away for 3 weeks vacation. Feel free to grab code. |
Support for DotCover configuration file added - fixes cake-build#1401
Support for DotCover configuration file added - fixes cake-build#1401
Hi I found some time on vacation to properly rebase branch and squash - now in pull #2213 |
…on-file' into develop * AdaskoTheBeAsT-feature/Support-for-dotCover-configuration-file: Support for DotCover configuration file added - fixes #1401
* release/0.30.0: (22 commits) (build) Updated version and release notes. (GH-2214) Use Environment.CommandLine directly and remove polyfill. (GH-2238) Add repository metadata to NuGet packages Added alias for checking if the current run is a dry run. Execute setup and teardown when dry running script. (GH-2233) Documented bootstrap argument (GH-2232) Document exclusive argument (GH-2234) Removed Mono from CakeOption Add XML comments for CakeTaskExtensions Fix CakeTaskExtensions accessibility (build) Change tool name & fix packaging (build) Added Cake.Tool package to parameters.cake Allow opting out from using working directory. (GH-2067) Cake .NET Core Tool package * Updates SDK * Addes Cake.Tool project * Fixes #2067 * Fixes #1644 Support for DotCover configuration file added - fixes #1401 Initialized all tool settings collection properties Failing tests for initialized tool settings collections (GH-2207) Update to NuGet 4.7.0 (GH-2220) Corrected documentation for InnoSetup alias (doc) Minor modification ...
As described in the help, dotCover can also be called with a
configuration file
:I guess this is especially interesting for specifying filters. Since they might be reused from within the IDE at some point.
The text was updated successfully, but these errors were encountered: