Contribution records
Contributors

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

Give credit to everyone
huijing hj_chen
2pha 2pha
hongpong HongPong organization(s): kor group
damien_vancouver damienvancouver volunteering
joachim joachim
kmonty kmonty
kappaluppa kappaluppa volunteering
niccottrell niccottrell
mangamike mangamike
bradallenfisher baf139
MattMeadows MattMeadows
alokvermaei alokvermaei
kclarkson kclarkson
rodtatham rodtatham
awelch awelch
cilefen cilefen
vmamidela vmamidela
bdanin bdanin
sandramandy sandramandy volunteering
beautifulmind beautifulmind organization(s): Joshi Consultancy Services
nachocode rmfranciacastillo volunteering
thalles thallesvf organization(s): CI&T
sylvain lavielle slavielle
Swetha Yarla sy-melity organization(s): Melity
aditya.n aditya.n organization(s): gai Technologies Pvt Ltd
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.