-
Notifications
You must be signed in to change notification settings - Fork 2.9k
fix(global): ensure that all globalOnly options can be set with Global Config
#39669
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
base: main
Are you sure you want to change the base?
Conversation
lib/config/global.spec.ts
Outdated
|
|
||
| // HACK | ||
| const defined = (GlobalConfig as any).OPTIONS; | ||
| console.log(globalOnlyOptions); |
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.
| console.log(globalOnlyOptions); |
lib/config/global.spec.ts
Outdated
| import { getOptions } from './options'; | ||
|
|
||
| describe('config/global', () => { | ||
| it('all', () => { |
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.
TODO
…bal Config As part of #9603, we intended to come back and make sure that all of our `globalOnly` configuration fields are set here, so they can be correctly updated by configuration (in various forms). As some configuration may not work if we do not set this, we should make sure that this is applied, as well as ensuring that there is a test to catch this requirement.
viceice
left a comment
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.
This will break renovate, as all thos options are filtered here and are no longer on RepoGlobalConfig
Line 70 in 78e5977
| delete result[option]; |
|
OK fair - so this is maybe the inverse? We should be making sure that |
|
We should re-review this (when we come round to it) to determine if #24115 has any pointers to things that should (not) be included |
Changes
As part of #9603, we intended to come back and make sure that all of our
globalOnlyconfiguration fields are set here, so they can be correctlyupdated by configuration (in various forms).
As some configuration may not work if we do not set this, we should make
sure that this is applied, as well as ensuring that there is a test to
catch this requirement.
Context
Please select one of the following:
AI assistance disclosure
Did you use AI tools to create any part of this pull request?
Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.
GPT-4.1
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
The public repository: