Contribution records
Contributors

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

Give credit to everyone
danthorne danthorne
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
bucefal91 bucefal91
tedbow tedbow organization(s): Acquia
millenniumtree millenniumtree
super_romeo super_romeo
mukeysh Mukeysh volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
therobyouknow therobyouknow
vindesh vindesh volunteering
shelane shelane
mohammed j. razem doublethink organization(s): Vardot
ahmad abbad ahmad-abbad volunteering organization(s): Vardot customer(s): Vardot
rajab natshah RajabNatshah organization(s): Vardot
Git commit message
Commit types
  • 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

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.