Contribution records
Contributors

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

Give credit to everyone
lucastockmann lucastockmann organization(s): undpaul
jstoller jstoller volunteering organization(s): California Science Center
cb cb volunteering
tapscolam tapscolaM
michaellander michaellander
seanb seanB
jsacksick jsacksick
recrit recrit
aschiwi aschiwi organization(s): undpaul
nancydru nancyw
idflood idflood organization(s): Stimul.ch
pbuyle mongolito404 organization(s): Floe design + technologies
pol Pol volunteering
klokie klokie volunteering
emmanvazz emmanvazz volunteering
CatherineOmega CatherineOmega volunteering
mshdevx maxdev organization(s): Youwe
loopduplicate loopduplicate organization(s): Hook 42
herved herve001
kevinquillen kevinquillen organization(s): Velir
geoffray gwarnants
capellic capellic
jkopel jkopel volunteering
damienmckenna damienmckenna organization(s): Current
jeroen.b jeroen.b organization(s): .VDMi/
thomas.claes thomas.claes
manu manu manumanu
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.