Contribution records
Contributors

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

Give credit to everyone
amateescu amateescu customer(s): Pfizer, Inc., Tag1 Consulting, Inc.
plach plach organization(s): Tag1 Consulting, Inc.
cosmicdreams cosmicdreams
masipila masipila volunteering
dillix dillix
karishmaamin karishmaamin organization(s): Specbee
nikhil_110 Nikhil_110 organization(s): Material
catch catch organization(s): Third and Grove
anmolgoyal74 anmolgoyal74
stborchert stborchert organization(s): undpaul
immaculatexavier immaculate.x volunteering organization(s): Material customer(s): Drupal India Association
nicxvan nicxvan
smustgrave smustgrave organization(s): Mobomo
tanuj. DrTanuj volunteering organization(s): Material customer(s): Drupal India Association
berdir berdir organization(s): MD Systems GmbH
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
andypost andypost volunteering organization(s): Skilld
larowlan larowlan organization(s): PreviousNext
alexpott alexpott organization(s): Acro Commerce, Thunder
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.