Contribution records
Draft
Contributors

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

Give credit to everyone
KoCo KoCo
shanethehat shanethehat
marazmus marazmus
seaneffel seaneffel
MetsArt MetsArt
davidcsonka davidcsonka
danielhonrade danielhonrade
cfbauer cfbauer
calefilm calefilm
chrisla clwdesign
sunset_bill sunsetbill
djhspence djhspence
samwillc samwillc
Snufkinski Snufkinski
docker docker
jlea9378 jlea9378
memcinto memcinto
jmlavarenne blackguard
yoran scholiers Varengas
it-cru it-cru
Eleven-Drupal Eleven-Drupal
jenlampton jenlampton
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.