Contribution records
Contributors

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

Give credit to everyone
sun sun
catch catch organization(s): Tag1 Consulting, Inc., Third and Grove
donquixote donquixote volunteering
jibran jibran volunteering
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
amitgoyal amitgoyal
anavarre anavarre organization(s): Acquia
alvar0hurtad0 alvar0hurtad0 organization(s): ASPgems
jonhattan jonhattan
almaudoh almaudoh
mile23 Mile23 volunteering
berdir berdir organization(s): MD Systems GmbH
alexpott alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
andypost andypost volunteering organization(s): Skilld
xano Xano organization(s): Druid
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
larowlan larowlan organization(s): PreviousNext
phenaproxima phenaproxima organization(s): Acquia
oriol_e9g oriole9g organization(s): Diputació de Barcelona
bircher bircher volunteering organization(s): Nuvole
vijaycs85 vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
stefan.r stefan.r
wim leers wimleers organization(s): Acquia
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.