Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
lauriii organization(s): Acquia
catch organization(s): Third and Grove
rkoller
ckrina organization(s): Lullabot
joachim volunteering organization(s): Factorial.io
smustgrave organization(s): Mobomo
hooroomoo organization(s): Acquia
duadua
rajeshreeputra volunteering organization(s): Shivswarajya Inc.
larowlan organization(s): PreviousNext
quietone organization(s): PreviousNext
alexpott organization(s): Acro Commerce, Thunder
aaronmchale volunteering
sakthi_dev organization(s): Specbee customer(s): Drupal India Association
ressa organization(s): Ardea
ameymudras organization(s): Salsa Digital
dscl volunteering organization(s): Acquia
samundrasharma volunteering
yiyiSHAO
longwave organization(s): Full Fat Things
_pratik_ volunteering customer(s): Drupal India Association
kunal.sachdev organization(s): Acquia
tim.plunkett organization(s): Acquia
yash.rode organization(s): Acquia
omkar.podey organization(s): Acquia
xjm volunteering organization(s): xjm
kentr volunteering
mgifford
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.