Issue
Contribution records
Contributors

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

Give credit to everyone
neclimdul organization(s): APQC
agoradesign
djg_tram
alex0412
pivica volunteering
sokru volunteering
joachim
ttnt
freelock organization(s): Freelock
caspervoogt organization(s): Plethora
rgpublic
fomenkoandrey
stefaniev
ac
trebormc volunteering
snlnz
acbramley organization(s): PreviousNext customer(s): Service NSW
akic
avpaderno volunteering
imclean organization(s): Digital Ink
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
joaopauloscho organization(s): Zoocha
greggles organization(s): Morris Animal Foundation
divyesh19 organization(s): TATA Consultancy Services
nickdickinsonwilde organization(s): Taoti Creative
scambler organization(s): Zoocha
benjifisher organization(s): FRUITION
kevster
gueguerreiro volunteering
japerry organization(s): Acquia
maurizio.ganovelli
Andrew.Dmytriv volunteering organization(s): Drupal Ukraine Community, ZANZARRA Drupal Agency
petr illek volunteering organization(s): Annertech
kim.pepper organization(s): PreviousNext
darren oh volunteering organization(s): Cognizant Softvision
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.