Issue
Contribution records
Contributors

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

Give credit to everyone
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
cilefen
mahalingam_cs organization(s): TATA Consultancy Services
valthebald
catch organization(s): Tag1 Consulting, Inc., Third and Grove customer(s): American Federation of Teachers
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): American Federation of Teachers
paulocs organization(s): CI&T
vikashsoni volunteering organization(s): Zyxware Technologies
nicer
ranjith_kumar_k_u organization(s): Zyxware Technologies
spokje
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
bhanu951 volunteering
deepalij organization(s): Salsa Digital
acbramley organization(s): PreviousNext
smustgrave organization(s): Mobomo
lauriii organization(s): Acquia
larowlan organization(s): PreviousNext
munish.kumar volunteering organization(s): Material customer(s): Drupal India Association
isa.bel organization(s): Zoocha
ayush.khare organization(s): OpenSense Labs customer(s): DrupalFit
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.