Contribution records
Contributors

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

Give credit to everyone
pwolanin pwolanin
xjm xjm organization(s): Acquia
jhedstrom jhedstrom
catch catch organization(s): Third and Grove
yesct YesCT
tstoeckler tstoeckler
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
alexpott alexpott
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
amateescu amateescu
jamesoakley JamesOakley
larowlan larowlan organization(s): PreviousNext
Mixologic Mixologic organization(s): Drupal Association
David_Rothstein drothstein volunteering
mile23 Mile23 volunteering
mondrake mondrake
webchick webchick organization(s): Acquia
dww dww volunteering
tedbow tedbow organization(s): Acquia
jibran jibran volunteering organization(s): PreviousNext
berdir berdir organization(s): MD Systems GmbH
eelkeblok eelkeblok organization(s): One Shoe
gábor hojtsy goba organization(s): Acquia
star-szr star-szr
wim leers wimleers organization(s): Acquia
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
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.