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

Allow any scope casing for Conventional Commits #828

Closed
wants to merge 1 commit into from

Conversation

kripod
Copy link
Contributor

@kripod kripod commented Oct 16, 2019

Description

As the spec does not enforce any scope casing rules, I think that any casing may be used on behalf of repo maintainers.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@marionebl
Copy link
Contributor

Related to #767

@escapedcat
Copy link
Member

@kripod sorry, this is super old. Happy to merge this is in, if you can rebase it.

@kripod
Copy link
Contributor Author

kripod commented Mar 27, 2021

@escapedcat No worries, I’ve just opened a new PR – thank you for notifying me! 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants