only discover dependencies from known project types #10451
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
1 task
JoeRobich
approved these changes
Aug 15, 2024
kbukum1
approved these changes
Aug 16, 2024
kbukum1
force-pushed
the
dev/brettfo/nuget-restrict-file-extension
branch
from
d15121d
to
3da6d2a
Compare
imajes
pushed a commit
to imajes/dependabot-core
that referenced
this pull request
Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running NuGet dependency discovery, we should only process project types that are explicitly supported, namely
.csproj,.vbproj, and.fsproj. This is consistent with how it's done elsewhere in this repo, we just missed a spot.Fixes #10372