Contribution records
Contributors

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

Give credit to everyone
bettibio bettibio
arlinsandbulte arlinsandbulte
karens karens
Durrok Durrok
recoil recoil
Peel Peel
awasson awasson
davepotts davepotts
justindavis justindavis
gazwal gazwal
manop manop
llribas llribas
allella allella
lee20 lee20
marvil07 marvil07
guignonv guignonv
mschaal mschaal
Fogg Fogg
rjl rjl
polmaresma polmaresma
paganwinter paganwinter
tomgf tom
kekkis kekkis
nehelek nehelek
gianfrasoft gianfrasoft
shaneonabike ShaneOnABike
jdelgama jdelgama
coolreddy coolreddy
carn1x carn1x
isaac.niebeling isaac.niebeling
jayelless jayelless
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.