Issue
Contribution records
Contributors

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

Give credit to everyone
vuil organization(s): Bulpros Consulting, JAKALA (formerly FFW)
asya_asina volunteering organization(s): DrupalJedi
davps volunteering organization(s): DrupalJedi
samvada_jain_m organization(s): Specbee
nikitagupta organization(s): Material customer(s): Drupal India Association
shaktik volunteering organization(s): Material customer(s): Drupal India Association
msuthars organization(s): QED42 customer(s): Drupal India Association
megha_kundar
mschudders
kapilv volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
willempje2
xpersonas
esod organization(s): Memorial Sloan Kettering Cancer Center
segi organization(s): Cheppers
gurvan
bygeoffthompson
ralkeon
maacl
byacoubi
kemsnake
renew
dcdenison volunteering
alezu
nelo_drup
alorenc
lahoosascoots
gisle organization(s): Hannemyr Nye Medier AS customer(s): Ramsalt Lab
Shreevasa Tantry organization(s): Specbee
suresh prabhu parkala organization(s): Specbee
meena.bisht organization(s): QED42 customer(s): Drupal India Association
Pooja Ganjage organization(s): Asentech LLC
proweb.ua
artis.bajars
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.