Issue
Contribution records
Contributors

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

Give credit to everyone
nkoporec volunteering organization(s): Agiledrop - Your Trusted Drupal Teammates
trichers
manuga organization(s): Diputació de Barcelona
oriol_e9g organization(s): Diputació de Barcelona
kalpaitch volunteering
griffincox
hypertext200 volunteering
scott_euser volunteering organization(s): Fat Beehive, Soapbox
SriHarshaRavi
keshavv volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
farnoosh volunteering
sgurlt volunteering organization(s): Bright Solutions GmbH
nathaniel
flickerfly volunteering
yas volunteering
smaz organization(s): Five Mile Media
p4trizio organization(s): Elicos
ndobromirov organization(s): JAKALA (formerly FFW)
rwam
megachriz organization(s): WebCoo
ddrozdik volunteering organization(s): Five Jars
rsvelko
Christopher Riley
rajab natshah organization(s): Vardot
Vignesh soundararajan
scott.whittaker volunteering
prashant.c volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
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.