Contribution records
Contributors

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

Give credit to everyone
dopry dopry
taqwa taqwa
Jomel Jomel
burgs burgs
drewish drewish
drupalninja99 jaykali
OnkelTem onkeltem
swill swill
drupalina drupalina
mkalbere mkalbere
parrottvision parrottvision
sonictruth sonictruth
mark_r mark_r
ChrisRut ChrisRut
zeezhao zeezhao
reformatt reformatt
giorgio79 giorgio79
scotjam scotjam
nicolash nicolash
cyberwolf Cyberwolf
alberto56 alberto56
Stalski stalski
sovarn sovarn
zilverdistel zilverdistel
dan_lennox dan
alexgreyhead alexharries
fizk fizk
eidolon night eidolonnight
nedim.hadzimahmutovic nedim.hadzimahmutovic
finn lewis ecofinn
Garrett Albright garrettalbright
glass.dimly glassdimly
mr.j mr.j
Git commit message
Commit types
  • 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

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.