Contribution records
Contributors

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

Give credit to everyone
quicksketch quicksketch
chx chx
dmitrig01 dmitrig01
aclight aclight
webernet webernet
starbow starbow
catch catch
KentBye kentbye
Rowanw Rowanw
dries dries
pwolanin pwolanin
BioALIEN BioALIEN
Bevan bevan
yoroy yoroy
Jaza jaza
robertdouglass robertDouglass
kika kika
grendzy grendzy
rumander rumander
johnalbin johnalbin
Bojhan bojhan
casey casey
sun sun
mustanggb akamustang
olarin Olarin organization(s): Kosada
xjm xjm organization(s): Agileana
bkosborne bkosborne organization(s): Princeton University
gábor hojtsy goba
anders.fajerson fajerstarter
wim leers wimleers
Stefan Nagtegaal Stefan Nagtegaal
damien tournoud damz
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.