Contribution records
Contributors

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

Give credit to everyone
tedbow tedbow
quicksketch quicksketch
theohawse theohawse
facilus93 facilus93
Marat Marat
JamieOurada JamieOurada
RedTop RedTop
ogorun ogorun
rpsu rpsu
machete1 machete1
robbertnl robbertnl
hovel hovel
sinuz sinuz
thinkingcap thinkingcap
upupax upupax
djschoone djschoone
djmy djmy
iwant2fly iwant2fly
CatherineOmega CatherineOmega
avner avner
TheDoctor TheDoctor
dsrikanth dsrikanth
nitebreed Nitebreed
spelcheck spelcheck
Polk Polk
chaugi chaugi
lavamind lavamind
droath droath
mjstone323 mjstone323
kbell kbell
liminu ealmuno
mustanggb akamustang
andypost andypost
crystaldawn drupalstarz
jarush jarush
jabraben jabraben
luco luco
MWiz MWiz
hernandezjd hernandezjd
vernond vernond
petednz petednz
fenstrat fenstrat
frank.tuma@gmail.com frank.tuma@gmail.com
Andy Dorman AndyDorman
Alexander Matveev AlexanderMatveev
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.