Contribution records
Draft
Contributors

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

Give credit to everyone
larowlan larowlan organization(s): PreviousNext
mxr576 mxr576 organization(s): Pronovix
catch catch organization(s): Third and Grove
jibran jibran volunteering
fubarhouse fubarhouse organization(s): PreviousNext
daffie daffie
alexpott alexpott organization(s): Acro Commerce
yogeshmpawar yogeshmpawar organization(s): QED42 customer(s): Drupal India Association
chetanbharambe chetan18 organization(s): QED42 customer(s): Drupal India Association
abhaypai Abhaypai_8 volunteering organization(s): Material
smustgrave smustgrave organization(s): Mobomo
acbramley acbramley organization(s): PreviousNext
donquixote donquixote organization(s): European Commission and European Union Institutions, Agencies and Bodies
godotislate godotislate volunteering
amber himes matz amberhimesmatz organization(s): Drupalize.Me
kristen pol kepol organization(s): Itty Bitty Byte customer(s): Salsa Digital
akhil babu AkhilBabu organization(s): QED42
ironnuts andrewfarq volunteering
berdir berdir organization(s): MD Systems GmbH
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.