Issue
Contribution records
Contributors

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

Give credit to everyone
jhodgdon
batigolix volunteering
yoroy
ifrik
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
xjm organization(s): Acquia
gnuget volunteering organization(s): Agaric
vijaycs85 organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
andypost volunteering organization(s): Skilld
webchick organization(s): Acquia
larowlan organization(s): PreviousNext
markhalliwell organization(s): Tag1 Consulting, Inc.
benjifisher organization(s): Isovera
joachim volunteering
andrewmacpherson volunteering
meeli volunteering
cameron tod organization(s): Acquia
amber himes matz organization(s): Drupalize.Me
pasan.gamage organization(s): PreviousNext
last call media
joachim namyslo
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.