Contribution records
Contributors

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

Give credit to everyone
shendric shendric
Crell Crell
amitaibu amitaibu
mrconnerton mrconnerton
micheas micheas
mrfelton mrfelton
creativenode creativenode
DizzyC DizzyC
joachim joachim
davidwhthomas davidwhthomas
jonathan_hunt jonathanhunt
spineless spineless
chrisschaub schaub123
bendev bendev
plonk marufaberlin
grasmash madmatter23
socialnicheguru SocialNicheGuru
drvdt drvdt
marcoscano marcoscano
psynaptic psynaptic
ndenhild ndenhild
robloach robloach organization(s): Kalamuna
kclarkson kclarkson
ezoulou ezoulou
tjcvd tjcvd
elusivemind elusivemind organization(s): ITCON Services Inc.
nwom nwom
irinaz irinaz volunteering organization(s): Fibonacci Web Studio
damien tournoud damz
Joel MMCC Joel_MMCC
BJ___ BJW
marc angles MarcAngles
Paul B PaulB
chris matthews ChrisMatthews volunteering
joseph.olstad joseph.olstad
alex.skrypnyk alex.skrypnyk organization(s): DrevOps
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.