Contribution records
Contributors

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

Give credit to everyone
chx chx
AjK karpuz
NaX nax
fago fago
satori1984 satori1984
jhm jhm
drewish drewish
fax8 fax8
Arto arto
drumm drumm
FiReaNGeL fireang3l
Veggieryan Veggieryan
dries dries
arthurf arthuregg
Firewolf Firewolf
ceardach ceardach
thepeter thepeter
webchick webchick
inforeto inforeto
magico magico
Mguel Mguel
relyod relyod
Chill35 chill35
ChrisKennedy chriskennedy
kweisblatt kweisblatt
asimmonds asimmonds
Clemens Clemens
shayne1012 shayne1012
heine heine
laura s lauras
killes@www.drop.org killes
siva.thanush siva.thanush
DocDJ-forum DocDJ-forum
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.