Skip to content
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

Merged
merged 30 commits into from
Jun 27, 2023

Conversation

viceice
Copy link
Member

@viceice viceice commented Mar 24, 2023

Changes

rename with migration

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@viceice viceice added breaking Breaking change, requires major version bump core:config Related to config capabilities and presets labels Mar 24, 2023
@viceice viceice requested a review from rarkins March 24, 2023 20:27
@viceice viceice mentioned this pull request Mar 24, 2023
28 tasks
lib/config/presets/common.ts Outdated Show resolved Hide resolved
docs/usage/config-presets.md Show resolved Hide resolved
@HonkingGoose
Copy link
Collaborator

This PR targets the main branch. Should this PR target v36 branch instead?

We probably don't want to accidentally release a v36 just for the rename from config:base to config:recommended. 🙈

@viceice
Copy link
Member Author

viceice commented Mar 30, 2023

We'll retarget when we prepare v36, until ten it's easier to rebase onto main.

rarkins and others added 6 commits May 10, 2023 09:05
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
@HonkingGoose
Copy link
Collaborator

@viceice I think we're working on v36 now, so it's probably a good time to re-target this PR to the v36 branch. 😉

@viceice viceice changed the base branch from main to v36 May 15, 2023 11:36
viceice and others added 3 commits May 15, 2023 13:37
Co-authored-by: Rhys Arkins <rhys@arkins.net>
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
@viceice viceice force-pushed the feat/presets/rename-base2recommend branch from 42d91d9 to b833e19 Compare May 15, 2023 11:37
@viceice viceice marked this pull request as ready for review May 15, 2023 11:37
@viceice viceice requested a review from rarkins May 15, 2023 11:37
@rarkins
Copy link
Collaborator

rarkins commented May 15, 2023

Does this handle the scenario where a self-hosted user has configured an onboardingConfig containing config:base? Ideally we should raise the actual onboarding PR with config:recommended not config:base

rarkins and others added 6 commits June 12, 2023 13:49
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
@rarkins rarkins merged commit 6b282e6 into v36 Jun 27, 2023
33 checks passed
@rarkins rarkins deleted the feat/presets/rename-base2recommend branch June 27, 2023 12:26
rarkins added a commit that referenced this pull request Jun 27, 2023
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>
rarkins added a commit that referenced this pull request Jul 1, 2023
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>
rarkins added a commit that referenced this pull request Jul 4, 2023
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>
rarkins added a commit that referenced this pull request Jul 4, 2023
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>
rarkins pushed a commit that referenced this pull request Jul 4, 2023
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
rarkins pushed a commit that referenced this pull request Jul 4, 2023
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
rarkins pushed a commit that referenced this pull request Jul 4, 2023
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
@dpprdan
Copy link

dpprdan commented Jul 20, 2023

@viceice Shouldn't


also become config:recommended?

@HonkingGoose
Copy link
Collaborator

@dpprdan Good catch, see issue:

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking Breaking change, requires major version bump core:config Related to config capabilities and presets
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename config:base -> config:recommended
5 participants