Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): Florida DrupalCamp
cachee cachee volunteering
crasx crasx volunteering organization(s): Bounteous
dangur dangur organization(s): AtypicalSavant
froboy froboy organization(s): ImageX customer(s): YMCA of the USA
hot_sauce hotsaucedesign volunteering organization(s): Lullabot
jimsmith JimSmith volunteering
keiserjb keiserjb volunteering organization(s): Academy of Model Aeronautics
markie markie organization(s): Kanopi Studios
mglaman mglaman organization(s): Acquia
mr_scumbag mr_scumbag organization(s): Code Journeymen customer(s): Code Journeymen
shaal shaal volunteering organization(s): Phase2
ultimike ultimike organization(s): DrupalEasy
ultrabob ultrabob organization(s): Kalamuna
weekbeforenext weekbeforenext
josh.fabean josh.fabean organization(s): Code Koalas
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.