Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
quietone organization(s): PreviousNext
mstrelan organization(s): PreviousNext
eojthebrave organization(s): Drupalize.Me
naveenvalecha organization(s): Morpht customer(s): Morpht
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
davidburns organization(s): Lullabot
vladimiraus organization(s): Tomato Elephant Studio
cmlara organization(s): DM13 Security LLC
ultimike organization(s): DrupalEasy
anwar_max volunteering organization(s): TA Digital customer(s): TA Digital
berdir organization(s): MD Systems GmbH customer(s): Schlütersche Fachmedien GmbH
zuernbernhard
mandclu volunteering organization(s): Acquia
tdnshah
avpaderno volunteering
solideogloria
dries
poker10 organization(s): ActivIT s.r.o.
luke.leber
greg boggs
joseph.olstad
darren oh volunteering
gábor hojtsy organization(s): Acquia
kristen pol organization(s): QuantCDN, Salsa Digital
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.