Contribution records
Contributors

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

Give credit to everyone
vollepeer vollepeer
rp7 rp7
thomjjames thomjjames
socialnicheguru SocialNicheGuru
falco010 Falco010 volunteering
opi opi volunteering
eelkeblok eelkeblok organization(s): One Shoe
lorenzs lorenzs volunteering
xiaodoudou xiaodoudou
timme77 timme77
idebr idebr organization(s): One Shoe
kumkum29 kumkum29
pol Pol volunteering
nicholasthompson njt1982 volunteering
matthiasm11 matthiasm11 organization(s): MM-Experience
jstoller jstoller volunteering organization(s): California Science Center
emmanvazz emmanvazz volunteering
jeroen.b jeroen.b organization(s): .VDMi/
Sebastien VR vanrise
sebastien m. smalot
das-peter daspeter organization(s): Cando
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.