Contribution records
Draft
Contributors

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

Give credit to everyone
jhodgdon jhodgdon
colan colan
dww dww
brian_c brian_c
selvakumar selvakumar122
asb asb
2dareis2do 2dareis2do
douggreen douggreen
ParisLiakos rootatwc
agileware agileware
cabita cabita
rcross rcross
vimalgoradiya vimalgoradiya
xjm xjm
pit_zavra pit_zavra
catch catch
jibran jibran
klonos klonos
swentel swentel
ianthomas_uk ianmthomasuk
gauravvvv Gauravmahlawat organization(s): OpenSense Labs
mitthukumawat mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
quietone quietone volunteering
johnv johnv
ñull com2
alan d. aland
joseph.olstad joseph.olstad
iosif.peterfi iosif.peterfi
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.