-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: sharedVariableName #33111
base: main
Are you sure you want to change the base?
feat: sharedVariableName #33111
Conversation
Needs testing on at least one real repo |
const groupName = result.spec; | ||
const specName = result.spec; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to avoid using the string groupName
at all in lib/modules/manager
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not familiar with why we needed grouping on Cocoapods
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's been there since originally implemented by @zharinov
FYI I want to have a similar concept for |
Co-authored-by: Michael Kriese <[email protected]>
Co-authored-by: Michael Kriese <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -305,6 +305,7 @@ export interface RenovateConfig | |||
statusCheckNames?: Record<StatusCheckKey, string | null>; | |||
env?: UserEnv; | |||
logLevelRemap?: LogLevelRemap[]; | |||
sharedVariableName?: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ Aung Ko
Changes
Replaces
groupName
in manager extract results withsharedVariableName
instead. I chose to keepgroupName
later for simplicity and backwards compatibility.Context
We should still group updates if they have shared variables, but separate the concept from manually-configured groupNames.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: