Contribution records
Contributors

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

Give credit to everyone
drewish drewish
dopry dopry
magico magico
keve keve
chx chx
dikini dikini
dmitrig01 dmitrig01
Frando frando
dries dries
RobRoy robroy
philippejadin philippejadin
catch catch
jpetso jpetso
mlncn mlncn
mikl mikl
robloach robloach
cburschka arancaytar
breyten breyten
aaron aaron
mfer mfer
vaish vaish
scroogie scroogie
Freso freso
Arto arto
quicksketch quicksketch
floretan floretan
litwol litwol
cwgordon7 cwgordon7
senpai senpai
sun sun
webchick webchick
samirnassar samirnassar
Susurrus susurrus
jhedstrom jhedstrom
robertdouglass robertDouglass
bdragon bdragon
meba meba
CalebD CalebD
Crell Crell
moshe weitzman weitzman
owen barton grugnog
Stefan Nagtegaal Stefan Nagtegaal
gábor hojtsy goba
Dave Cohen yogadex2
wim leers wimleers
keith.smith keithsmith
david strauss straussd
greg.harvey greg.harvey
smk-ka smk-ka
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.