Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
erikwebb
pwolanin
hefox
maximpodorov
mxr576 organization(s): Pronovix
ndobromirov
anybody organization(s): DROWL.de
rob230 volunteering organization(s): CTI Digital
catch organization(s): Tag1 Consulting, Inc. customer(s): American Federation of Teachers
avpaderno volunteering
br0ken volunteering organization(s): Drupal Ukraine Community, JAKALA (formerly FFW) customer(s): Drupal Ukraine Community, JAKALA (formerly FFW)
smustgrave organization(s): Mobomo
acbramley organization(s): PreviousNext
moshe weitzman
wim leers
daniel.nitsche
neslee canil pinto organization(s): Specbee
liam morland organization(s): OpenPlus
anchal_gupta organization(s): Material customer(s): Drupal India Association
nicxvan organization(s): nLightened Development LLC
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.