Contribution records
Contributors

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

Give credit to everyone
m3avrck m3avrck
webchick webchick
jacauc jacauc
BioALIEN BioALIEN
magico magico
dries dries
nedjo nedjo
Crell Crell
Steven unconed
umonkey umonkey
Frando frando
dvessel dvessel
ximo ximo
mfer mfer
drewish drewish
yched yched
gribnif gribnif
dkruglyak dkruglyak
bjaspan bjaspan
robloach robloach
caktux caktux
lilou lilou
markus_petrux markuspetrux
SeanBannister seanbannister
catch catch
bryancasler animelion
no2e no2e
Gaelan Gaelan
johnalbin johnalbin
klonos klonos
nod_ nod_
owen barton grugnog
Caleb G2 Caleb G2
morbus iff morbus
dave reid davereid
moshe weitzman weitzman
Christefano-oldaccount christo
wim leers wimleers
hass hass
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.