ignorePaths ignored, PRs created anyway #34620
-
How are you running Renovate?Self-hosted Renovate If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.Azure DevOps, Renovate 40.0.0-next.17 Please tell us more about your question or problemOne of our renovate target repos has a folder that should be left alone. No packages updated within it. We express that with
in our renovate.json file (as a top-level property). Yet we got a PR that updates several packages (due to grouping), including updating the csproj that we didn't want updated. Choice bits from the log show that it noticed the property:
But soon after it listed all the package files it found and it included the ignored paths (abbreviated for readability): DEBUG: Matched 66 file(s) for manager nuget: .config/dotnet-tools.json, Directory.Build.props, Directory.Build.targets, Directory.Packages.props, azure-pipelines/NuGetSbom.targets, global.json, src/InProc/Extensibility.VSPackage/Microsoft.VisualStudio.Extensibility.VSPackage.csproj, src/InProc/LegacyPackages/Directory.Build.props, src/InProc/LegacyPackages/Version17.12.12/Version17.12.12.csproj, src/OptProf.targets, src/Project/DebugHost/Microsoft.VisualStudio.Extensibility.Debugging.DebugHost.csproj (repository=devdiv/Gladstone) One of the packages updated within that csproj file was in fact recognized by renovate as coming from the path that we excluded:
What do we need to do to get renovate to ignore all projects with Logs (if relevant) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I found the answer: |
Beta Was this translation helpful? Give feedback.
I found the answer:
https://docs.renovatebot.com/nuget/#ignoring-package-files-when-using-presets