Contribution records
Contributors

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

Give credit to everyone
sandeepguntaka sandeepreddyg organization(s): Azri Solutions
lauriii lauriii organization(s): Druid
garnett2125 garnett2125
nkoporec nkoporec volunteering organization(s): Agiledrop - Your Trusted Drupal Teammates
bombjack bombjack volunteering
jeroent JeroenT organization(s): iO
jamiehollern jamiehollern volunteering organization(s): Amazee Labs
joshuami joshuami customer(s): City of Portland
vidorado vidorado
heddn lucashedding organization(s): MTech, LLC, Tag1 Consulting, Inc.
c.e.a C.E.A
moshe weitzman weitzman
dave reid davereid
eric.napier eknapier organization(s): CivicActions
kim.pepper kimpepper organization(s): PreviousNext
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.