Contribution records
Contributors

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

Give credit to everyone
indytechcook indytechcook
adamelleston adamelleston
damienmckenna damienmckenna organization(s): Current
ultimateboy ultimateboy
tregismoreira tregismoreira
donquixote donquixote
zd370 zd370
vflirt vflirt
tedbow tedbow
stevendeleus vectorbross
joelpittet joelpittet
kamescg kamescg
delzhand delzhand
recrit recrit
jwilson3 jwilson3 organization(s): Bluespark customer(s): HowlRound
ahillio ahillio
kristen pol kepol
nicolas bouteille NicolasBouteille
stefan.r stefan.r
evgeniysolodkov evgeniysolodkov
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.