Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
deepakkm organization(s): Acquia
chandu7929 volunteering
prabha1997 organization(s): QED42 customer(s): QED42
vishalkhode volunteering organization(s): Acquia
rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc. customer(s): Shivswarajya Inc.
ankitv18 volunteering organization(s): Acquia
phenaproxima organization(s): Acquia
mstrelan organization(s): PreviousNext
berdir organization(s): MD Systems GmbH
emptyvoid
heddn organization(s): MTech, LLC
suryabhi
romulasry
anybody volunteering organization(s): DROWL.de
znerol
borisson_ organization(s): Calibrate customer(s): Acerta
smulvih2 organization(s): Cinder Systems Corp.
mark_fullmer volunteering organization(s): University of Texas at Austin
acbramley organization(s): PreviousNext customer(s): Service NSW
jayemel
vipin.mittal18 volunteering organization(s): Acquia
kim.pepper organization(s): PreviousNext
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
joseph.olstad
rajab natshah organization(s): Vardot customer(s): Vardot
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.