NuGet: dependabot fails when a specific targets / props is unavailable

[GeertvanHorrik]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

NuGet

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

N/A

dependabot.yml content

N/A

Updated dependency

N/A

What you expected to see, versus what you actually saw

It would be good if there was a way (e.g. a variable) in MSBuild targets / props files to check whether it's currently running under dependabot (similar to release / debug).

In such case, we can exclude .props and .targets files that are not available during dependabot (but blocking updates).

Dependabot couldn't find a Eazfuscator.NET.targets

Dependabot requires a Eazfuscator.NET.targets to evaluate your .NET dependencies. It had expected to find one at the path: /Integration/MSBuild/Eazfuscator.NET.targets.

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response