Issue
Contribution records
Contributors

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

Give credit to everyone
alison volunteering
elusivemind organization(s): ITCON Services Inc.
devdesagar organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
hip
hockey2112
ushasharma84
austin_brian
inbalj volunteering
Coops_ volunteering
jungle volunteering
bakerlee
mirakolous organization(s): Kanopi Studios
zorax
timodwhit
dasginganinja organization(s): Lehigh University
alemadlei volunteering
Hitby
andypost volunteering organization(s): Skilld
ankithashetty volunteering organization(s): Specbee
balis_m
gantal organization(s): Elevated Third
pvasener
swatichouhan012 organization(s): Valuebound customer(s): Valuebound
waspper volunteering organization(s): Skilld
ollie222
minakshiPh organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
ARRC-Drupal-Chick
suresh prabhu parkala organization(s): Specbee
drupal.ninja03
john cook
max.parker organization(s): Unipro Ltd customer(s): Pfizer, Inc.
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.