Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
joachim volunteering
drumm organization(s): Drupal Association
frob organization(s): Clarity Innovations, Inc.
pasqualle volunteering
douggreen volunteering
tunic organization(s): Metadrop
jdleonard organization(s): Modern Biz Consulting
markdorison organization(s): Chromatic
damienmckenna organization(s): Current
rcodina
hestenet organization(s): Drupal Association
nicxvan
thursday_bw organization(s): Morpht
bbrala organization(s): SWIS
xurizaemon organization(s): Catalyst IT
rosk0 organization(s): Catalyst IT
achap
murz volunteering organization(s): EPAM customer(s): TVH
johnpitcairn
gordon organization(s): Heydon Consulting customer(s): Department of Customer Service, NSW
colan organization(s): Consensus Enterprises customer(s): Zivtech
feyp volunteering organization(s): werk21
ressa organization(s): Ardea
nevergone volunteering
mpotter organization(s): Phase2
cilefen volunteering
dave reid volunteering organization(s): Lullabot customer(s): Principal Financial Group
dmitry.korhov organization(s): EPAM
eduardo morales alberti volunteering organization(s): Metadrop
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.