Contribution records
Contributors

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

Give credit to everyone
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
wturrell wturrell volunteering
alexpott alexpott organization(s): Acro Commerce, Thunder
longwave longwave volunteering
berdir berdir organization(s): MD Systems GmbH
lpsolit LpSolit volunteering
matroskeen Matroskeen organization(s): DevBranch, Drupal Ukraine Community
catch catch organization(s): Third and Grove
andypost andypost volunteering organization(s): Skilld
keboca keboca
xjm xjm organization(s): Acquia
avpaderno avpaderno volunteering
dww dww organization(s): TEN7
nod_ nod_ volunteering
dagmar dagmar volunteering organization(s): Gizra
medha kumari kumarimedha09 volunteering organization(s): Dotsquares Ltd.
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.