Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
andrewozone organization(s): Bounteous
bsnodgrass organization(s): net2Community, Inc.
rkoller
johnpicozzi organization(s): EPAM
teknorah organization(s): Current
crasx organization(s): Bounteous
scorbine organization(s): Bounteous
cgreaten organization(s): Bounteous
adrianm6254 organization(s): net2Community, Inc.
arrow organization(s): Arrow One Solutions
jjcs227 volunteering
kleighm organization(s): Bounteous
kthull organization(s): Blue Drop Shop
mandclu volunteering organization(s): Acquia
mherchel
volkswagenchick organization(s): Red Hat
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.