Issue
Contribution records
Contributors

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

Give credit to everyone
taran2l organization(s): Lemberg Solutions
avpaderno volunteering
ozin organization(s): Lemberg Solutions
sjerdo volunteering organization(s): Synetic
ronlee
mustanggb
izmeez
pratik_kamble organization(s): QED42 customer(s): Drupal India Association
ayesh
anavarre organization(s): Acquia
mcdruid volunteering organization(s): Acquia
eliosh volunteering
cilefen
mfb
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
liam morland organization(s): University of Waterloo
joseph.olstad
gábor hojtsy organization(s): Acquia
steven jones organization(s): ComputerMinds
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.