Issue
Contribution records
Contributors

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

Give credit to everyone
hydra volunteering organization(s): erdfisch
tomsaw volunteering
millerrs
joe_carvajal organization(s): La Drupalera by Emergya
kmonty organization(s): BKJ Digital
owilliwo organization(s): Alithya
junkuncz organization(s): drunomics
fago organization(s): drunomics
slideaway
carolpettirossi organization(s): ImageX
nelo_drup
igorgoncalves organization(s): ImageX
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
juagarc4
smulvih2 organization(s): Cinder Systems Corp.
joel_osc organization(s): OpenPlus
dan612 organization(s): Hounder
joseph.olstad
liam morland organization(s): OpenPlus, Scouting Waterloo Region
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.