Issue
Contribution records
Contributors

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

Give credit to everyone
jwilson3 organization(s): Bluespark
catch organization(s): Third and Grove
damienmckenna organization(s): Current
mandclu
WidgetsBurritos organization(s): Rackspace
heddn organization(s): MTech, LLC
mmjvb volunteering
chi
solideogloria
andypost volunteering organization(s): Skilld
pasqualle volunteering
cweagans volunteering
xjm organization(s): Acquia
tonytheferg
feyp volunteering organization(s): werk21
Mixologic organization(s): Drupal Association
tedbow organization(s): Acquia
quietone organization(s): PreviousNext
greg boggs
kristen pol organization(s): Hook 42 customer(s): Hook 42
gábor hojtsy organization(s): Acquia
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.