Issue
Contribution records
Contributors

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

Give credit to everyone
gabrielolferrari organization(s): CI&T customer(s): Johnson & Johnson
perpignan
mark_fullmer volunteering organization(s): University of Texas at Austin
jedihe volunteering
vladimiraus organization(s): Tomato Elephant Studio customer(s): Must Do Brisbane
redeight organization(s): 95Visual
igonzalez
kyuubi volunteering
ollibolli
eyilmaz volunteering organization(s): JAKALA (formerly FFW)
rik_deuzeman
superlolo95
abellata
dqd volunteering organization(s): MAROQQO studios
kimberleycgm organization(s): Zoocha
mfrosch volunteering
saurabh29p
pifagor volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
alex_optim organization(s): GOLEMS GABB customer(s): GOLEMS GABB
harshadananjaya
krug volunteering
tetem
kgaut
knyshuk.vova organization(s): Drupal Ukraine Community, Internetdevels
aadesh.verma
texas-bronius organization(s): Ocelot
laura.gates
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.