dotnet-affected
dotnet-affected copied to clipboard
.NET tool for determining which projects are affected by a set of changes. Useful for large projects or monorepos.
Minor issue, it might mark projects as affected when they are not necessarily. NuGet 6.2 introduces central package management and drops the preview flag. However they also support overriding individual...
We should add a JSON output formatter that outputs changed/affected projects. This is useful for automation purposes.
Testing that net7 preview 1 works :)
I've never built an MSBuild Task before so I don't really know, but I was thinking that maybe if we can use the underlying logic behind discovering affected projects inside...
According to twitter, it may not be that hard: https://twitter.com/jarkreij/status/1414528552549093376/photo/1 Something to research on
Currently, when using `--repository-path`, only `.csproj` files will be discovered. When using a `--solution-path`, all projects inside the solution will be taken into account. We should discover all MSBuild projs...
When testing only what's affected, the coverage report will show incorrect results. For example, given this project structure: 1. Project.Shared 2. Project (.1) 3. Project.Tests (depends on .2) 4. Shared.Tests...
Currently when there's any exception (except for the `NoChangesException`) full stacktrace is shown to the end user. We should throw known exceptions and using the error middleware convert them to...
Hi, I'm running a Github workflow and getting the following error: `Unhandled exception: System.InvalidOperationException: Couldn't find Git Commit or Branch with name develop in repository /home/runner/work/[...]/[...]/.git/` The command that runs...
- [ ] Update `System.CommandLine` and related to latest version - [ ] Remove custom DI logic from CLI. To be replaced with [the BinderBase](https://docs.microsoft.com/en-us/dotnet/standard/commandline/dependency-injection). - [ ] Add logging...