Contribution records
Contributors

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

Give credit to everyone
mbaynton mbaynton
cilefen cilefen
RavindraSingh it.ravindrasingh volunteering organization(s): Material
dawehner dereine volunteering organization(s): Tag1 Consulting, Inc.
berdir berdir organization(s): MD Systems GmbH
fabianx Fabianx customer(s): Drupal Association
lauriii lauriii organization(s): Druid
chx chx
vijaycs85 vijaycs85 volunteering organization(s): Capgemini
catch catch
kgoel kg organization(s): Forum One
webchick webchick organization(s): Acquia
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
tim.plunkett tim.plunkett organization(s): Acquia
wim leers wimleers volunteering organization(s): Acquia
claudiu.cristea claudiucristea organization(s): Webikon
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.