Issue
Contribution records
Contributors

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

Give credit to everyone
chx
seantwalsh
xjm organization(s): Acquia
dawehner volunteering customer(s): Drupal Association
effulgentsia organization(s): Acquia
aneek
joelpittet
cpj
fabianx volunteering organization(s): Tag1 Consulting, Inc.
imiksu
berdir organization(s): MD Systems GmbH
mikey_p
cb
killua99
lauriii volunteering
dimaro organization(s): La Drupalera by Emergya
larowlan volunteering organization(s): PreviousNext
miroslavbanov
googletorp organization(s): Reveal IT
jaredsmith organization(s): Bluehost
yesct
catch
jcnventura
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
lokapujya organization(s): Babson College
willzyx
pwolanin organization(s): Acquia
alimac organization(s): University of Illinois at Chicago
tim.plunkett
star-szr volunteering
kim.pepper
wim leers organization(s): Acquia
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.