Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
xjm organization(s): Acquia
bnjmnm organization(s): Acquia
jhedstrom organization(s): Phase2
aleevas organization(s): Skilld
Percy101 volunteering
hardik_patel_12 organization(s): QED42 customer(s): Drupal India Association
swatichouhan012 organization(s): Valuebound customer(s): Valuebound
mrinalini9 organization(s): Material customer(s): Drupal India Association
fskreuz organization(s): Portland Webworks
BenVercammen
joshmiller organization(s): Urban Institute
anchal_gupta organization(s): Material customer(s): Drupal India Association
vacho organization(s): Skilld
nikhil_110 organization(s): Material
smustgrave organization(s): Mobomo
kevinquillen organization(s): Velir
gauravvvv organization(s): Axelerant customer(s): Drupal India Association
samuel.mortenson organization(s): Acquia
tim.plunkett organization(s): Acquia
bendeguz.csirmaz organization(s): Cheppers
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
ravi.shankar organization(s): OpenSense Labs
suresh prabhu parkala organization(s): Specbee
andrea.cividini organization(s): FRUITION
dk-massive organization(s): University of Minnesota
liam morland organization(s): OpenPlus
mithun s organization(s): QED42 customer(s): QED42
robert-arias
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.