Contribution records
Contributors

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

Give credit to everyone
catch catch organization(s): Third and Grove
alexpott alexpott organization(s): Acro Commerce, Thunder
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
xjm xjm organization(s): Acquia
longwave longwave organization(s): Full Fat Things
jibran jibran organization(s): PreviousNext
heddn lucashedding organization(s): MTech, LLC
andypost andypost volunteering organization(s): Skilld
larowlan larowlan organization(s): PreviousNext
daffie daffie
martin107 martin107 volunteering
Lal_ abhilal007 volunteering organization(s): QED42
taran2l Taran2L organization(s): Drupal Ukraine Community, Lemberg Solutions
dpi dpi volunteering organization(s): PreviousNext customer(s): Service NSW
wim leers wimleers organization(s): Acquia
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
ravi.shankar ravi.shankar organization(s): OpenSense Labs
tim.plunkett tim.plunkett organization(s): Acquia
deepak goyal DeepakGoyal organization(s): Material customer(s): Drupal India Association
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.