dotnet-affected

dotnet-affected copied to clipboard

Deleted file does not affect project

7

I've noticed that if file deletion is the only change, `dotnet-affected` does not include the project in the list of affected. File deletion can break compilation of the project, so...

batkaevruslan

Support discovering projects through an existing Traversal project

1

dotnet-affected currently supports discovering projects from an existing solution file via `--solution-path`, or by recursively searching the repository path (either the current working directory or the path specified via `--repository-path`)....

jrusbatch

Ability to distinguish between changed and affected projects

9

Currently the tool helpfully reports all the changed or affected projects, both in `.proj` and in `json`. One thing that is missing is to be able to know what project...

AlexeyRaga

Bumps the dotnet group with 6 updates: | Package | From | To | | --- | --- | --- | | [BenchmarkDotNet](https://github.com/dotnet/BenchmarkDotNet) | `0.13.5` | `0.14.0` | | [BenchmarkDotNet.Diagnostics.Windows](https://github.com/dotnet/BenchmarkDotNet)...

dependabot[bot]

Flag to include not only the dependents, but also the dependencies

3

Our team uses `dotnet-affected` ( :heart: ) to only built/test/deploy the affected projects in our monorepo. However due to various small issues between the dotnet tools (build/test/publish) and traversal files,...

BenjaBobs

closes #81

jensk-dev