Contribution records
Contributors

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

Give credit to everyone
takim takim
megachriz megachriz volunteering organization(s): WebCoo
kumkum29 kumkum29
arskiainen arskiainen organization(s): Mirum Agency
pvbergen pvbergen volunteering organization(s): iqual AG
francescoq FrancescoQ
anthonybr anthonybr
bibo bibo
revija revija
omarlopesino omarlopesino volunteering organization(s): Metadrop
BarisW barisw organization(s): ronder
le72 le72
lobsterr LOBsTerr
camoa camoa organization(s): Acquia
matthieu_collet matthieu_collet
fbreckx fbreckx
shkiper shkiper volunteering
toprak toprak
inst inst
mazze mazze
trickfun trickfun
westerix westerix
yurg yurg
flodevelop Flodevelop
david.qdoscc qdoscc
artis.bajars artis.bajars
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.