Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
heyyo
phenaproxima organization(s): Acquia
marcus_johansson organization(s): FreelyGive customer(s): Acquia
mrdalesmith organization(s): FreelyGive
anjaliprasannan volunteering organization(s): QED42
prashant.c volunteering organization(s): QED42 customer(s): Drupal India Association
kristen pol organization(s): Salsa Digital
arianraeesi customer(s): 1xINTERNET
joshua1234511 volunteering organization(s): Axelerant
harivansh organization(s): OpenSense Labs customer(s): DrupalFit
gafioni organization(s): E-Sepia Web Innovation
cadence96 volunteering organization(s): SeeD EM
erichomanchuk organization(s): Foster Interactive Inc.
brtamas
bharat.kelotra
adhariwal organization(s): Axelerant
ahmad khader volunteering organization(s): Vardot
a.dmitriiev organization(s): 1xINTERNET
abhisekmazumdar organization(s): Dropsolid customer(s): Dropsolid
vidit.anjaria organization(s): QED42
merilainen organization(s): Mearra (formerly known as Wunder)
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.