Contribution records
Contributors

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

Give credit to everyone
mikey_p mikey_p
Vidarls olegu
GothGargoyle GothGargoyle
blb blb
christefano christefano
niklp niklp
akahn akahn
socialnicheguru SocialNicheGuru
sime sime
Leech Leech
shrop shrop
tuongaz tuongaz
AdrianB AdrianB
MadtownLems MadtownLems
kentr kentr
sunnydeveloper emmairwin
geerlingguy geerlingguy
bspellmeyer bspellmeyer
neotohin neotohin
estherswhite estherswhite
xmacinfo xmacinfo
bisonbleu bisonbleu
dynamicdan dynamicdan
agileadam agileadam
mewren mewren
pratik60 pratik60
Internet Internet
protools protools
pribeh pribeh
Sarah10 Sarah10 volunteering
kubrt kubrt
drupalastic drupalastic volunteering
moshe weitzman weitzman
HotDrupal.com HotDrupal.com
decibel.places decibel.places
Larry Jones LarryJones
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.