Contribution records
Draft
Contributors

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

Give credit to everyone
pounard pounard
fubhy sumsi
amateescu amateescu
catch catch
damiankloip damiankloip
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios) customer(s): Drupal Association
sun sun
Crell Crell organization(s): Palantir.net
xano Xano organization(s): Druid
berdir berdir organization(s): MD Systems GmbH
aspilicious aspilicious
borisson_ borisson_ volunteering organization(s): Calibrate, iO
RavindraSingh it.ravindrasingh volunteering organization(s): Material
cosmicdreams cosmicdreams volunteering
sjerdo sjerdo volunteering organization(s): Synetic
andypost andypost volunteering organization(s): Skilld
alexpott alexpott organization(s): Acro Commerce, Thunder
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
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.