-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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(presets)!: rename config:base
to config:recommended
#21136
Conversation
This PR targets the We probably don't want to accidentally release a |
We'll retarget when we prepare v36, until ten it's easier to rebase onto main. |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
gitAuthor discover for GitLab now prefers the field `commit_email` over `email`. BREAKING CHANGE: GitLab gitAuthor will change from the account's "email" to "commit_email" if they are different.
Set `{ dot: true }` for minimatch. BREAKING CHANGE: dot files will now be included by default for all minimatch results
@viceice I think we're working on |
Co-authored-by: Rhys Arkins <rhys@arkins.net>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
42d91d9
to
b833e19
Compare
Does this handle the scenario where a self-hosted user has configured an onboardingConfig containing |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
gitAuthor discover for GitLab now prefers the field `commit_email` over `email`. BREAKING CHANGE: GitLab gitAuthor will change from the account's "email" to "commit_email" if they are different.
Set `{ dot: true }` for minimatch. BREAKING CHANGE: dot files will now be included by default for all minimatch results
a759d49
to
f0ca46e
Compare
Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de>
Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de>
Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de>
Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de>
Closes #12024 Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de> BREAKING CHANGE: Preset config:base is now called config:recommended
Closes #12024 Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de> BREAKING CHANGE: Preset config:base is now called config:recommended
Closes #12024 Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Bastian Gutschke <bastian.gutschke@gmx.de> BREAKING CHANGE: Preset config:base is now called config:recommended
@viceice Shouldn't
also become config:recommended ?
|
@dpprdan Good catch, see issue: |
Changes
rename with migration
Context
config:base
->config:recommended
#12024Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: