Contribution records
Draft
Contributors

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

Give credit to everyone
nath nath
janusman janusman
anrikun anrikun
sutharsan sutharsan
moritzz moritzz
shady_gun shady_gun
BenK benk
xjm xjm
floretan floretan
summit summit
shaneonabike ShaneOnABike
ckidow CKIDOW
asb asb
bsuttis bsuttis
pheraph pheraph
chales chales
mastoll mastoll
drupalfan81 drupalfan81
vivianspencer vivianspencer
markchitty thisliquidspace
aristeides aristeides
splash112 marktonino
tonychiu25 tonychiu25
Bodo Maass Bodo_Maass
kari.kaariainen kari.kaariainen
Renee S Reinette
ñull com2
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.