Issue
Contribution records
Contributors

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

Give credit to everyone
kkasson
mpdonadio organization(s): DiD Agency
berdir organization(s): MD Systems GmbH
nicxvan
edmonkey
wombatbuddy
pameeela
tatianag
xurizaemon organization(s): Catalyst IT
jannakha volunteering organization(s): Tomato Elephant Studio customer(s): Australian Competition and Consumer Commission (ACCC)
dww organization(s): TEN7
spokje organization(s): Chromatic
tannguyenhn organization(s): Department of Customer Service, NSW, Lil Engine customer(s): Department of Customer Service, NSW
ranjith_kumar_k_u organization(s): Zyxware Technologies
vladimiraus organization(s): Tomato Elephant Studio customer(s): Australian Competition and Consumer Commission (ACCC)
dieuwe organization(s): Sparks Interactive
alexpott organization(s): Acro Commerce, Thunder
raman.b organization(s): OpenSense Labs
Madhu kumar volunteering organization(s): Zyxware Technologies
pooja saraah organization(s): Material customer(s): Drupal India Association
shubham chandra volunteering organization(s): Dotsquares Ltd.
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.