Can't ignore php update #18905
Can't ignore php update
#18905
-
Hey, Im starting to integrate Renovate which goes fine. I get 2 PRs one for my PHP deps and one for my NPM deps. However a standalone PR is generate for the PHP update itself which i would love to ignore in general. In general i also have no idea where he is getting it from since it is not a packagist data reference if im correct? Any ideas? Current output
Config{
"platform": "azure",
"endpoint": "https://org.visualstudio.com/",
"repositories": [
"Infrastructure/sla"
],
"extends": [
":dependencyDashboard",
":ignoreModulesAndTests",
":rebaseStalePrs",
":semanticCommitsDisabled",
":separateMajorReleases",
":combinePatchMinorReleases",
":enableVulnerabilityAlerts",
":label(Renovate)",
":gitSignOff"
],
"vulnerabilityAlerts": {
"extends": [
":labels(Security CVE)"
],
"rangeStrategy": "bump"
},
"labels": ["dependencies"],
"lockFileMaintenance": {
"enabled": true
},
"rollbackPrs": true,
"ignoreUnstable": true,
"recreateClosed": true,
"rangeStrategy": "bump",
"rebaseWhen": "auto",
"packageRules": [{
"matchDatasources": ["packagist"],
"groupName": "PHP packages",
"groupSlug": "PHP"
}, {
"matchDatasources": ["npm"],
"groupName": "NPM packages",
"groupSlug": "NPM",
"stabilityDays": 3
}],
"major": {
"enabled": false
}
} |
Beta Was this translation helpful? Give feedback.
Answered by
rarkins
Nov 14, 2022
Replies: 1 comment 6 replies
-
This also will not do the trick btw: "packageRules": [{
"matchManagers": ["composer"],
"excludePackageNames": ["php"]
},{
"matchDatasources": ["packagist"],
"groupName": "PHP packages",
"groupSlug": "PHP"
}, {
"matchDatasources": ["npm"],
"groupName": "NPM packages",
"groupSlug": "NPM",
"stabilityDays": 3
}], |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This rule achieves nothing, no matter where you put it.
match*
andexcluse*
rules are just used for matching, and do nothing unless there's also an action to do. Therefore you need this, and it can go anywhere in the packageRules: