Contribution records
Contributors

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

Give credit to everyone
ckrina ckrina organization(s): Lullabot
e0ipso e0ipso volunteering organization(s): Lullabot
gauravvvv Gauravmahlawat organization(s): Axelerant customer(s): Drupal India Association
meeni_dhobale meeni_dhobale volunteering organization(s): QED42
finnsky finnsky organization(s): Skilld
m4olivei m4olivei organization(s): Lullabot
quietone quietone organization(s): PreviousNext
pdureau pdureau volunteering
nod_ nod_ volunteering organization(s): Très Bien Tech customer(s): Liip, OPTASY, Palantir.net, Vardot
smustgrave smustgrave organization(s): Mobomo
trackleft2 trackleft2 volunteering organization(s): The University of Arizona
pooja_sharma pooja_sharma volunteering organization(s): QED42 customer(s): Drupal India Association
wim leers wimleers organization(s): Acquia
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.