Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
breathingrock
eshta
cweagans
xjm organization(s): Acquia
webchick organization(s): Acquia
tkoleary organization(s): Acquia
catch organization(s): Third and Grove
yoroy organization(s): Roy Scholten
ifrik
droplet
katzilla organization(s): Reinblau
webflo organization(s): UEBERBIT GmbH
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
mohit_aghera volunteering organization(s): Axelerant
berdir organization(s): MD Systems GmbH
aaronmchale volunteering
saschaeggi organization(s): Unic
bnjmnm organization(s): Acquia
smustgrave organization(s): Mobomo
elijah lynn organization(s): NBCUniversal
tim.plunkett organization(s): Acquia
hass
quietone organization(s): PreviousNext
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.