Contribution records
Contributors

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

Give credit to everyone
edgarpe EdgarPE
shabbir Shabbir organization(s): Trigyn Technologies Ltd
ameymudras mudrasamey volunteering
joelpittet joelpittet
prateekS prateekS volunteering
imalabya malabya organization(s): Valuebound
kostyashupenko kostyashupenko organization(s): Skilld
Thirugnanam Thirugnanam volunteering
Saphyel Saphyel volunteering
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
timisoreana timisoreana organization(s): Skilld
idebr idebr organization(s): One Shoe
jwilson3 jwilson3 organization(s): Bluespark
bronzehedwick bronzehedwick organization(s): Memorial Sloan Kettering Cancer Center
maninders Maninders organization(s): Material
paintingguy audiokid
jordana jordana volunteering
jhodgdon jhodgdon
mikeohara mikeohara
star-szr star-szr volunteering organization(s): Northern Commerce
nitesh pawar NiteshP organization(s): Trigyn Technologies Ltd
laxman.ghavte laxmang organization(s): Faichi Solutions Pvt Ltd
emma.maria emma.maria
manjit.singh Manjit.Singh organization(s): Material
Vidushi Mehta VidushiMehta organization(s): gai Technologies Pvt Ltd
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.