Issue
Contribution records
Contributors

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

Give credit to everyone
dyannenova organization(s): Acquia
adrian83
anton-staroverov volunteering organization(s): Highweb
yoroy organization(s): Roy Scholten
naveenvalecha volunteering
tedbow organization(s): Acquia
hudri
eclipsegc organization(s): Acquia
andrewmacpherson volunteering organization(s): Annertech
jive01
webchick organization(s): Acquia
altrugon organization(s): Affinity Bridge
freelylw
mlncn organization(s): Agaric customer(s): Drutopia, Teachers with GUTS
xjm organization(s): Acquia
dsquaredb volunteering organization(s): DSquaredB Consulting, LLC, Hook 42
sharique volunteering organization(s): Acquia
andypost volunteering organization(s): Skilld
nod_ volunteering organization(s): Acquia
pcate
bobemoe
tim.plunkett organization(s): Acquia
wim leers organization(s): Acquia
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.