Issue
Contribution records
Contributors

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

Give credit to everyone
klemendev volunteering organization(s): Pylo
dasginganinja organization(s): Lehigh University
phjou
darvanen
indrajithkb organization(s): Material customer(s): Drupal India Association
maenjuel
neclimdul organization(s): APQC
satyaki_dutta
artusamak organization(s): Happyculture
gobinathm organization(s): TATA Consultancy Services customer(s): Johnson & Johnson
bryandenijs organization(s): Triquanta
pavelculacov
johnpitcairn
jcnventura organization(s): 1xINTERNET
promes volunteering
hideaway organization(s): jobiqo - job board technology
andypost volunteering organization(s): Skilld
fabsgugu
eugene_bsk organization(s): EPAM
ysamoylenko organization(s): EPAM
andrey.troeglazov organization(s): DrupalJedi
OCTOGONE.dev
orlando.thoeny organization(s): Namics customer(s): Namics
joshua.boltz
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.