Contribution records
Contributors

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

Give credit to everyone
titicaca37 titicaca37
hobo hobo
Mario2 Mario2
simonoh simonoh
comrax comrax
tomfallowfield tomfallowfield
kenwest kenwest
KathleenG KathleenG
sher1 sher1
ufku ufku
rodonnell rodonnell
loewenconsulting loewenconsulting
pal_ur pal_ur
igorski igorski
nguyenbn nguyenbn
verta verta
saepl saepl
quotientix rbf
Mark0s81 Mark0s81
laurenco laurenco
bibimo bibimo
jasonabc mycommerce
wheelercreek wheelercreek
maddentim maddentim
lupus78 lupus78
cjtemple cjtemple
cpo cpo
nancydru nancyw
ronino ronino
bramick bramick
mtunay mtunay
gregarios gregarios
curt2199 curt2199
mthomas mthomas
revnoah revnoah
thalles thallesvf organization(s): CI&T
t-wheeler t-wheeler
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.