Contribution records
Contributors

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

Give credit to everyone
Letharion Letharion
merlinofchaos merlinofchaos
rogical rogical
suldan suldan
Yuri Yuri
yurtboy yurtboy
hixster hixster
flefle flefle
davidwhthomas davidwhthomas
CogitoSrl CogitoSrl
malberts malberts
svajlenka svaj
nicholaswyoung nicholaswyoung
roberttstephens roberttstephens
japerry japerry organization(s): Drupal Association
mustanggb akamustang
afoster aidanfoster
jibran jibran
paskainos paskainos
BillyTom BillyTom
damienmckenna damienmckenna
michelle Michelle
maxplus maxplus
jantoine antoinesolutions
barwonhack barwonhack
gstout gstout
bkosborne bkosborne
shortspoken moritzpeikert
zabelc zabelc
kissmedve kissmedve
kurtronaldmueller@gmail.com kurtronaldmueller@gmail.com
b-prod bprod
fox mulder foxmulder
geek-merlin geek-merlin
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.