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

docs: use enabled instead of true for semanticCommits config #8835

Merged
merged 2 commits into from
Feb 24, 2021

Conversation

HonkingGoose
Copy link
Collaborator

@HonkingGoose HonkingGoose commented Feb 24, 2021

Changes:

  • Replace true with enabled

Context:

I've linked issue #8833, as I think it helps with fixing the issue, but I'm not sure if it fully fixes it...
It seems we need to do more than just fixing the docs???

Fixes #8833.

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 tick one)

I have verified these changes via:

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

@rarkins rarkins enabled auto-merge (squash) February 24, 2021 10:12
@rarkins rarkins merged commit bbeda09 into renovatebot:master Feb 24, 2021
@HonkingGoose HonkingGoose deleted the patch-1 branch February 24, 2021 10:17
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 24.63.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[docs] semanticCommits config option type
3 participants