You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If i run dotnet-affected against my repo with pending changes, the result is showing affected changes also caused by files that are not staged.
Is it justifiable to introduce a switch to ignore unstaged files? Or is my use case to exotic? Reason
I use dotnet-affected in a git pre-commit hook, determing which projects are affected by the commit. In these projects I then add a "update_by_dependency.txt" file which triggers Nerdbank GitVersioning to bump the version of the affected project.
As a workaround I currently stash the unstaged files before I run dotnet-affected.
The text was updated successfully, but these errors were encountered:
If i run dotnet-affected against my repo with pending changes, the result is showing affected changes also caused by files that are not staged.
Is it justifiable to introduce a switch to ignore unstaged files? Or is my use case to exotic?
Reason
I use dotnet-affected in a git pre-commit hook, determing which projects are affected by the commit. In these projects I then add a "update_by_dependency.txt" file which triggers Nerdbank GitVersioning to bump the version of the affected project.
As a workaround I currently stash the unstaged files before I run dotnet-affected.
The text was updated successfully, but these errors were encountered: