Issue
Contribution records
Contributors

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

Give credit to everyone
ropaolle
djg_tram
ronan
dwalker51
Tezza
llepere
Salasta
jtwalters
tuccio
afoster
v1adimir
ahimsauzi
sgaddis
Shai
mahtoranjeet
emosbaugh
ilechcod
phreadom
ntigh52
erok415
giorgosk
ballboy
RandyK
mermentau
mrweiner
polskikrol
aitala
smitty
kruser
bsenftner
greta_drupal
nikosnikos
brightbold
heddn
crutch
couloir007
ergophobe
Leeteq
ohthehugemanatee
sbakshian
mjross
francoud
jonokuchi
GopherWild
hcethatsme volunteering
xaqrox
djschoone organization(s): d-Media
scotwith1t
dasigr
couturier volunteering
chandeepkhosa organization(s): 2Toucans
brankoc volunteering
Rick Nashleanas
-j
shawn dearmond
deadtech@gmail.com
ar-jan
pere orga
albert volkman
yuriy mudriy volunteering organization(s): DEWEB Studio customer(s): Drupal Ukraine Community
ivnish volunteering
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.