Contribution records
Contributors

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

Give credit to everyone
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
arifkhn46 arifkhan volunteering
amateescu amateescu customer(s): Pfizer, Inc.
alexpott alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
heddn lucashedding organization(s): MTech, LLC
hamrant karpilenko organization(s): Drupal Ukraine Community, Five Jars, Open Y customer(s): Drupal Ukraine Community
liquidcms liquidcms
tobiberlin tobiberlin
mxr576 mxr576 organization(s): Pronovix
nwom nwom
mohit_aghera mohit_aghera organization(s): QED42
catch catch organization(s): Third and Grove
hswong3i hswong3i organization(s): PantaRei Design Limited (Hong Kong)
smustgrave smustgrave organization(s): Mobomo
larowlan larowlan organization(s): PreviousNext
dscl dscl volunteering organization(s): Acquia
mstrelan mstrelan organization(s): PreviousNext
peter feddo peterfeddo
stefan.korn stefan.korn organization(s): Stefan Korn - Webentwicklung
ankit agrawal AnkitAgrawal volunteering organization(s): Axelerant
joseph.olstad joseph.olstad
perfectcu.be perfectcube volunteering
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.