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.
Why
Per #356 (comment)
What
Fixes following issues
Changes proposed in this pull request:
nuget
for directories that only contain theDirectory.Build.props
filelabel
manually (dependabot set it by its own if it is seft unset)Probably we should use the generated PRs only for sake of "tracking". Thanks to it we are notified about new versions. After we create PRs like #436 we can then check if the PRs are automatically closed.
Some of them we can close manually if we do not want to bump the dependency.
A similar approach is used in https://github.com/open-telemetry/opentelemetry-go and https://github.com/open-telemetry/opentelemetry-go-contrib. The only issue is that it generates a lot of spam GitHub notifications...
Testing
Check https://github.com/pellared/opentelemetry-dotnet-instrumentation-dependabot/pulls
Generating dependabot
I executed
find . -type f -name '*.csproj' | sed -r 's|/[^/]+$||' | sort | uniq
to all directories containing*.csproj
.Then I have written a little Go program to generate the yml file
Probably we could make a Nuke target that does it instead.