Contribution records
Contributors

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

Give credit to everyone
develcuy develCuy
steveadamo steveadamo
jogebau jogebau
ldbl ldbl
peddecke peddecke
preventingchaos gcopenhaver
scotthenning scotthenning
mikeytown2 mikeytown2
restyler troy
George2 george2
gunzip gunzip
dropchew dropchew
mgladding mgladding
Heilong Heilong
mitchell mitchell
tomhung tomhung
jstoller jstoller
redijedi redijedi
shawnspqr shawnspqr
luxx luxx
TC44 TC44
Aerodynamo Aerodynamo
jweberg jweberg
himagarwal himagarwal
drupov mrupal
pimousse98 pimousse98
jrabeemer Giovanni_Glass
mrfelton mrfelton
benone benone
GeekyLass GeekyLass
gilcpd gilcpd
k3vin k3vin_git
summit summit
not_Dries_Buytaert not_Dries_Buytaert
ygerasimov ygerasimov
Flying Drupalist Flying_Drupalist
design.er stefanriske
mani.atico mani.atico
kars-t karst
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.