Contribution records
Contributors

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

Give credit to everyone
greggles greggles organization(s): CARD.com
pwolanin pwolanin
meba meba
casey casey
aaronbauman aaronbauman
eric_a erica
mgifford mgifford organization(s): OpenConcept Consulting Inc.
rteijeiro rteijeiro organization(s): Tieto
dawehner dereine volunteering
naveenvalecha naveenvalecha organization(s): Morpht customer(s): Morpht
quietone quietone volunteering
humansky humansky volunteering organization(s): Princeton University
sime sime organization(s): Department of Customer Service, NSW
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
nikhil_110 Nikhil_110 organization(s): Material
bhanu951 Bhanu951 volunteering
pooja_sharma pooja_sharma volunteering organization(s): QED42 customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
alexpott alexpott organization(s): Acro Commerce, Thunder
amanbtr72 amanmansuri72 organization(s): cmsMinds customer(s): Drupal Association
mr.baileys mr.baileys organization(s): Calibrate
bas.hr sbacelic
hetal.solanki Hetal.Solanki volunteering organization(s): cmsMinds
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.