Issue
Contribution records
Contributors

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

Give credit to everyone
robloach
Crell organization(s): Palantir.net
fabianx volunteering
catch organization(s): Third and Grove
xjm organization(s): Acquia
quicksketch
effulgentsia
donquixote volunteering
neclimdul
sun
andypost volunteering organization(s): Skilld
eclipsegc
berdir organization(s): MD Systems GmbH
mile23 volunteering
jhedstrom
webchick organization(s): Acquia
tstoeckler organization(s): erdfisch
dawehner
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
Mixologic organization(s): Drupal Association
mgifford organization(s): OpenConcept Consulting Inc.
heddn organization(s): MTech, LLC
fgm organization(s): OSInet
bradjones1 volunteering
alexpott organization(s): Acro Commerce, Thunder
moshe weitzman
wim leers organization(s): Acquia
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.