Contribution records
Contributors

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

Give credit to everyone
fabske fabske
kevroc kevroc
mccrodp mccrodp
wwwwoicn wwwwoicn
torontoseohelp torontoseohelp
jarush jarush
jeremycaldwell eternalistic
lammertsm lammertsm
drewkeller drewkeller
sergebw sergebw
BenK benk
itrain itrain
marcoka eanima
elgandoz elgandoz
juan_g juan_g
fivestarstravel fivestarstravel
dngankam dngankam
basco basco
stephthegeek stephthegeek
goody815 goody815
karing semperit
richH richH
sheila8stamp sheila8stamp
jeffwidman jeffwidman
Deepika.chavan deepc104
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.