Issue
Contribution records
Contributors

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

Give credit to everyone
sasanikolic organization(s): Google Summer of Code
aditya4478
smustgrave organization(s): Mobomo
gauravvvv organization(s): Axelerant customer(s): Drupal India Association
nod_ organization(s): Eclipse Foundation, Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
vladimiraus organization(s): Tomato Elephant Studio customer(s): Relationships Australia Queensland
santosh_verma organization(s): Material customer(s): Drupal India Association
bnjmnm organization(s): Acquia
bramdriesen volunteering organization(s): Sopra Steria
lauriii organization(s): Acquia
swatidhurandhar organization(s): Material
pragati_kanade organization(s): QED42 customer(s): Drupal India Association
akshayadhav volunteering organization(s): QED42
guptahemant volunteering organization(s): QED42
sourabhjain organization(s): Valuebound
stanzin volunteering
finnsky organization(s): Skilld
quietone organization(s): PreviousNext
sakthivel m organization(s): QED42 customer(s): Drupal India Association
mithun s customer(s): QED42
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.