Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
kingdutch organization(s): Open Social
e0ipso volunteering organization(s): Lullabot
catch organization(s): Third and Grove customer(s): Drupal Association
fgm volunteering organization(s): OSInet
mikelutz volunteering organization(s): ICON Interactive
mxr576 organization(s): Pronovix
klausi organization(s): jobiqo - job board technology
mpp organization(s): AmeXio Fuse customer(s): District09
berdir organization(s): MD Systems GmbH
chi
xjm organization(s): HeroDevs, Salsa Digital, xjm
alexpott volunteering organization(s): Acro Commerce, Thunder
andypost volunteering organization(s): Skilld
daffie
aaronmchale
mondrake volunteering
mstrelan organization(s): PreviousNext
mfb
phenaproxima organization(s): Acquia
bbrala volunteering organization(s): SWIS
longwave organization(s): Full Fat Things
larowlan organization(s): PreviousNext
drunken monkey volunteering
gábor hojtsy organization(s): Acquia
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
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.