Contribution records
Contributors

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

Give credit to everyone
rajeshreeputra Rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc. customer(s): Shivswarajya Inc.
ankitv18 ankitv18 volunteering organization(s): Acquia
svenryen svenryen organization(s): Ramsalt Lab
deepakkm deepakkm organization(s): Acquia
chandu7929 chandu7929 volunteering
redseujac redseujac
hswong3i hswong3i organization(s): PantaRei Design Limited (Hong Kong)
asamoahboateng asamoahboateng
perrypierre perrypierre organization(s): Ramsalt Lab
ericvl EricVL
heddn lucashedding organization(s): MTech, LLC, Tag1 Consulting, Inc.
vipin.mittal18 vipin.mittal18 volunteering organization(s): Acquia
vishal choudhary VishalChoudhary 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.