Contribution records
Contributors

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

Give credit to everyone
rachel_norfolk rachel_norfolk organization(s): Open Development Ltd
kostyashupenko kostyashupenko organization(s): Skilld
idebr idebr organization(s): One Shoe
nitinsp NitinSP organization(s): Clarion Technologies
emallove emallove
armyguyinfl dkowalec
radioflyer radioflyer volunteering
akalata akalata
nathanc nathanc
edutrul edutrul volunteering
aburrows abdesignuk volunteering
gnuget gnuget volunteering organization(s): Agaric
ccjjmartin ccjjmartin volunteering
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
manjit.singh Manjit.Singh organization(s): Material
emma.maria emma.maria organization(s): TES Global
star-szr star-szr volunteering organization(s): Northern Commerce
davidmcgee1021@gmail.com davidmcgee volunteering
Vidushi Mehta VidushiMehta volunteering organization(s): gai Technologies Pvt Ltd customer(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.