Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
matt_paz
romixua organization(s): EPAM
pifagor volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
anybody organization(s): DROWL.de
yepa organization(s): Happy Coding
maskedjellybean volunteering
abhisekmazumdar volunteering organization(s): QED42 customer(s): Drupal India Association
phjou
Webbeh organization(s): Georgia Institute of Technology
simgui8 volunteering
murz organization(s): Digiterra
geoffreyr
hswong3i organization(s): PantaRei Design Limited (Hong Kong)
diegodalr3 volunteering
grevil volunteering organization(s): DROWL.de
andypost volunteering organization(s): Skilld
hfernandes organization(s): ImageX
smustgrave organization(s): Mobomo
joelpittet organization(s): The University of British Columbia
carolpettirossi organization(s): ImageX
tim.plunkett organization(s): Acquia
Vidushi Mehta organization(s): gai Technologies Pvt Ltd
andrea.cividini organization(s): FRUITION
a.milkovsky organization(s): Drupal Austria, k-digital
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.