Contribution records
Draft
Contributors

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

Give credit to everyone
dalin dalin organization(s): Four Kitchens customer(s): American Federation of Teachers, NYU New York University
utkarsh_33 Utkarsh_33 volunteering organization(s): Acquia
arunkumark arunkumark volunteering organization(s): Material customer(s): Drupal India Association
poker10 poker10 organization(s): ActivIT s.r.o.
dpi dpi organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
shalini_jha shalini_jha organization(s): QED42 customer(s): QED42
benjifisher benjifisher volunteering
rkoller rkoller
joaopauloc.dev joaopauloc.dev organization(s): ImageX
samitk samit.310 organization(s): Material customer(s): Drupal India Association
eric.vvf ericimagexmedia
dcam dcam
quietone quietone organization(s): PreviousNext
nicxvan nicxvan organization(s): nLightened Development LLC
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.