Issue
Contribution records
Contributors

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

Give credit to everyone
lauriii organization(s): Acquia, Druid
joelpittet volunteering
tvn organization(s): Drupal Association
tstoeckler volunteering
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
cilefen
naveenvalecha volunteering
davidhernandez organization(s): JAKALA (formerly FFW)
izmeez
phenaproxima organization(s): Acquia
jmuzz
jurriaanroelofs
neograph734
megan_m
pingwin4eg volunteering
andypost volunteering organization(s): Skilld
webchick organization(s): Acquia
mherchel
cweagans volunteering
gaborkurucz organization(s): Pronovix
ivnish
saltednut
andrewmacpherson volunteering
ckrina organization(s): Lullabot
rachel_norfolk organization(s): Drupal Association
anruether organization(s): Geeks4Change
jasonawant organization(s): Nerdery customer(s): Nestle Purina PetCare - United States
xjm organization(s): Acquia
joachim organization(s): Factorial.io
quietone organization(s): PreviousNext
geerlingguy organization(s): Midwestern Mac, LLC
Jeff Burnz
geek-merlin organization(s): Geeks4Change, MachbarMacher
gábor hojtsy 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.