Contribution records
Contributors

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

Give credit to everyone
bensnyder bensnyder
kruser kruser
bigimprintwebmaster bigimprintwebmaster
acbramley acbramley
tuthanh tuthanh
susannab susannab
alauddin alauddin
knalstaaf knalstaaf
jcisio jcisio
jelo jelo
mrpauldriver MrPaulDriver
wavesailor wavesailor
haleagar haleagar
bmango bmango
cscoleman cscoleman
npcoder npcoder volunteering
summit summit volunteering
darkodev darko_hrgovic
griffinhere griffinhere
erok415 erok415 volunteering organization(s): Molly Duggan Associates
renguer0 renguer0 volunteering
timfletcher timfletcher volunteering
caw67 caw67
ishmael-sanchez ishmaelsanchez
rich.yumul rich.yumul
Mario Baron Mario Baron
Kristina Katalinic Webmar-Design
pere orga netol
bil.meb bilel.mebarki
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.