Issue
Contribution records
Contributors

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

Give credit to everyone
tomzoocha organization(s): Zoocha
nikhil_110 organization(s): Material
markconroy organization(s): Annertech
smustgrave organization(s): Mobomo
Aadhar_Gupta organization(s): OpenSense Labs customer(s): DrupalFit
mrinalini9 organization(s): Material customer(s): Drupal India Association
lauriii organization(s): Acquia
arunkumark volunteering organization(s): Material customer(s): Drupal India Association
rpayanm organization(s): Agileana
larowlan organization(s): PreviousNext
catch organization(s): Third and Grove
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
star-szr volunteering
ashutosh ahirwal organization(s): Specbee customer(s): Specbee
rishabh vishwakarma organization(s): OpenSense Labs customer(s): DrupalFit
Vidushi Mehta organization(s): gai Technologies Pvt Ltd
saurav-drupal-dev volunteering organization(s): Material customer(s): Drupal India Association
liam morland organization(s): OpenPlus, Scouting Waterloo Region
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.