Issue
Contribution records
Contributors

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

Give credit to everyone
alexpott organization(s): Acro Commerce, Thunder
larowlan organization(s): PreviousNext
longwave organization(s): Full Fat Things
kingdutch organization(s): Open Social
cilefen
aaronmchale volunteering
andypost volunteering organization(s): Skilld
xjm volunteering
catch organization(s): Third and Grove
mondrake volunteering
fgm organization(s): OSInet
effulgentsia organization(s): Acquia
joachim volunteering organization(s): Factorial.io
daffie
pasqualle volunteering
bircher volunteering organization(s): Nuvole
soul88
taran2l organization(s): Lemberg Solutions
dpi organization(s): PreviousNext
christianadamski
mstrelan organization(s): PreviousNext
spokje volunteering
tr
vladimiraus organization(s): Tomato Elephant Studio
berdir organization(s): MD Systems GmbH
smustgrave organization(s): Mobomo
markdorison organization(s): Chromatic
frevda
duadua
drubb volunteering
bbrala volunteering organization(s): SWIS
moshe weitzman
tim.plunkett organization(s): Acquia
kim.pepper 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.