Issue
Contribution records
Contributors

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

Give credit to everyone
robloach
sdmunoz
ZenDoodles
jessebeach
oresh
philipz
sam152
benjy
rootwork
ckrina
rpayanm
lewisnyman organization(s): Mearra (formerly known as Wunder)
mortendk
cosmicdreams volunteering
nuez
pazhyn organization(s): AnyforSoft
andriyun
andypost organization(s): Skilld
eleleka organization(s): Skilld
valentine94 organization(s): Drupalway
dpetruk volunteering
simply021 organization(s): Develomon
rudraram organization(s): Axelerant
nod_ organization(s): Smile
komalk organization(s): Material customer(s): Drupal India Association
samiullah organization(s): Salsa Digital
anoopsingh92 organization(s): Valuebound customer(s): Valuebound
smustgrave organization(s): Mobomo
ishmael-sanchez
wim leers
emma.maria
manjit.singh organization(s): Material
volodymyr.oliinyk
hass
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.