Contribution records
Contributors

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

Give credit to everyone
Crell Crell
cburschka arancaytar
catch catch
chx chx
webchick webchick
sinasalek sinasalek
profix898 profix898
cwgordon7 cwgordon7
demeester_roel demeesterroel
breyten breyten
nancydru nancyw
dopry dopry
karens karens
webernet webernet
BioALIEN BioALIEN
theborg theborg
dropcube dropcube
meba meba
marcingy marcingy
starbow starbow
dries dries
pwolanin pwolanin
jaydub jaydub
robertdouglass robertDouglass
maartenvg maartenvg
recidive recidive
floretan floretan
Mongi Mongi
carlmcdade carlmcdade
ksenzee ksenzee
coupet coupet
dmitrig01 dmitrig01
owahab owahab
Susurrus susurrus
ax ax
donquixote donquixote
etaroza taroza
wim leers wimleers
moshe weitzman weitzman
keith.smith keithsmith
Stefan Nagtegaal Stefan Nagtegaal
killes@www.drop.org killes
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.