Issue
Contribution records
Contributors

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

Give credit to everyone
mikeocana volunteering organization(s): Promet Source
cilefen
jhodgdon
laranajim volunteering
wiifm volunteering
BarisW organization(s): ronder
catch organization(s): Third and Grove
maximpodorov
Collins405
ollie222
tameeshb organization(s): Google Summer of Code
danielveza
volkswagenchick organization(s): Kanopi Studios
altback volunteering
andrewmacpherson volunteering organization(s): Annertech
vacho organization(s): Skilld
mradcliffe organization(s): Kosada
sjerdo organization(s): Synetic
mcdruid organization(s): Acquia
fabianx volunteering organization(s): Tag1 Consulting, Inc.
dom. volunteering
nils.destoop volunteering organization(s): Mearra (formerly known as Wunder)
uzmaabdulrasheed1@gmail.com volunteering
Diane Bryan
tim.plunkett organization(s): Acquia
chris burge organization(s): University of Nebraska
joseph.olstad
Git commit message
Commit types
  • 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

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.