Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
sun
marcingy
timos
hefox
joachim
jibran
juanjo_vlc
varghese volunteering
nachosalvador organization(s): Ymbra
Zemelia organization(s): Drupal Ukraine Community, Internetdevels
mahtab_alam organization(s): Valuebound
rodrigoaguilera organization(s): Ymbra
unrealauk organization(s): AnyforSoft customer(s): Drupal Ukraine Community
itamair volunteering
kpv organization(s): DrupalBASE
junaidpv organization(s): Detlus customer(s): Wickwood Marketing
fernly organization(s): Dropsolid customer(s): District09
anas_maw organization(s): Coders Enterprise Web & Mobile Solutions
payel_g
imot3k
shashank5563
ericb1021
bkline
phoang volunteering
janec
sukr_s volunteering
solene_ggd organization(s): Maetva
asghar
lazzyvn
ericmaster
damien tournoud
Chris Gillis
anandhi karnan organization(s): Material customer(s): Drupal India Association
dinh bao tran
kevinquillen organization(s): Velir
Git commit message
Commit types
  • 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

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.