Contribution records
Contributors

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

Give credit to everyone
scor scor
berdir berdir organization(s): MD Systems GmbH
krlucas krlucas
blueminds divamys
lokapujya lokapujya
damiankloip damiankloip
undertext undertext
dawehner dereine volunteering
chx chx
mgifford mgifford
jeroent JeroenT organization(s): iO
nlisgo nlisgo
piyuesh23 piyuesh23 organization(s): QED42
kerby70 kerby70 organization(s): Blink Reaction (now part of FFW)
m1r1k m1r1k
mile23 Mile23 volunteering
subhojit777 subhojit777 volunteering organization(s): Material
amitgoyal amitgoyal
andypost andypost organization(s): Skilld
s_leu s_leu organization(s): MD Systems GmbH
dustinleblanc dustinleblanc volunteering
borisson_ borisson_ volunteering
daffie daffie
catch catch
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
znerol znerol
webchick webchick organization(s): Acquia
stefan.r stefan.r
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.