Contribution records
Contributors

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

Give credit to everyone
somes somes
faheebi faheebi
liupascal liupascal
user654 user654
johnv johnv
modstore modstore
muhammadanaskhan muhammadanaskhan
emilianodelau emilianodelau
tbenice tbenice
kevinquillen kevinquillen
khan2ims khan2ims
drupalnix drupalnix
jacerider JaceRider
charlied charlied
one_hoopy_frood one_hoopy_frood
rohittiwarirvt rohittiwarirvt
danielphenry danielphenry
Countzero Countzero
allenthehusband allenthehusband
mooru mooru
webexpertjsh webexpertjsh
royerd royerd
superelectron superelectron volunteering
kris77 Kris77
lubwn lubwn
Bright Web Design Bright Web Design
steven jones darthsteven
albert volkman avolkman
fgjohnson@lojoh.ca fgjohnson
danny englander danny-englander
uceap-web uceap-web
marco aurelio rocca MarcoAurelioRocca
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.