Issue
Contribution records
Contributors

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

Give credit to everyone
dawehner
davidhernandez volunteering
mpdonadio
cilefen
klausi
damienmckenna
gisle
yesct
dman
David_Rothstein volunteering
fabianx volunteering
cweagans
colan
srjosh
jthorson
gabesullice
kreynen organization(s): University of Colorado Boulder
attiks
jhodgdon
plazik
webchick organization(s): Acquia
randallknutson
fuzzy76
balazswmann
Mixologic organization(s): Drupal Association
chx
vbouchet
greggmarshall
greggles
kscheirer volunteering
heddn organization(s): MTech, LLC
darol100
pixelsweatshop
effulgentsia organization(s): Acquia
mikl volunteering
webel volunteering
pingwin4eg volunteering
kattekrab organization(s): Creative Contingencies
joachim
Homotechsual organization(s): MJCO
mlncn organization(s): Agaric
geerlingguy volunteering
tvn organization(s): Drupal Association
catch organization(s): Third and Grove
matt v.
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.