Issue
Contribution records
Contributors

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

Give credit to everyone
bailleux
marcoscano volunteering
seanb
dnebrich
lamp5 organization(s): abventor
joel_osc organization(s): OpenPlus
berdir organization(s): MD Systems GmbH
catch organization(s): Tag1 Consulting, Inc., Third and Grove customer(s): American Federation of Teachers
demonde
mistrae
sleitner
maddentim
mrshowerman organization(s): BRANDCODE
pbouchereau volunteering
anybody organization(s): DROWL.de
grevil volunteering organization(s): DROWL.de
smustgrave organization(s): Mobomo
kostyashupenko organization(s): Skilld
renukakulkarni volunteering
rahulrasgon organization(s): QED42 customer(s): Drupal India Association
visios
larskleiner
quotientix
quietone organization(s): PreviousNext
jonesui
OCTOGONE.dev
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
bs pavan organization(s): Material
amin.ankit organization(s): QED42
martijn de wit organization(s): Ablerz
shree.yesare organization(s): Acquia
priya gupta organization(s): Cognizant Technology Solutions
frocha volunteering
transmitter
lauriii organization(s): Acquia
drase15
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.