Issue
Contribution records
Contributors

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

Give credit to everyone
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
rlnorthcutt organization(s): Acquia
iuana organization(s): Softescu
pameeela volunteering
nareshbw volunteering
andrewmacpherson volunteering
bcizej organization(s): Agiledrop - Your Trusted Drupal Teammates
avpaderno
phenaproxima organization(s): Acquia
dpi organization(s): PreviousNext
aaronmchale volunteering
smustgrave organization(s): Mobomo
larowlan organization(s): PreviousNext
lauriii organization(s): Acquia
berdir organization(s): MD Systems GmbH
bnjmnm organization(s): Acquia
acbramley organization(s): PreviousNext customer(s): Service NSW
chr.fritsch organization(s): Thunder
bruce.yuen volunteering
yash.rode organization(s): Acquia
wim leers organization(s): Acquia
chris matthews
sumit saini volunteering
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.