Issue
Contribution records
Contributors

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

Give credit to everyone
dawehner volunteering
cilefen
berdir organization(s): MD Systems GmbH
20th volunteering
alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
Munavijayalakshmi organization(s): Valuebound
mile23 volunteering
derheap volunteering
jofitz organization(s): ComputerMinds
sutharsan organization(s): ronder
mohit1604 organization(s): Google Summer of Code
effulgentsia organization(s): Acquia
amateescu customer(s): Pfizer, Inc.
kristiaanvandeneynde organization(s): Factorial.io
catch organization(s): Third and Grove
claudiu.cristea organization(s): Webikon
tim.plunkett organization(s): Acquia
savkaviktor16@gmail.com organization(s): Skilld
wim leers organization(s): Acquia
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.