Skip to content

Allow any scope casing for Conventional Commits#828

Closed
kripod wants to merge 1 commit intoconventional-changelog:masterfrom
kripod:patch-1
Closed

Allow any scope casing for Conventional Commits#828
kripod wants to merge 1 commit intoconventional-changelog:masterfrom
kripod:patch-1

Conversation

@kripod
Copy link
Copy Markdown
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
Copy Markdown
Contributor

Related to #767

@escapedcat
Copy link
Copy Markdown
Member

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

@kripod
Copy link
Copy Markdown
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