Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): Kanopi Studios
ahughes3 ahughes3 volunteering
andrewozone andrewozone organization(s): Bounteous
bfodeke bfodeke
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
catapipper catapipper
salimlakhani sl4drupal volunteering
shrop shrop organization(s): Current
jcl324 JCL324 volunteering
barberod barberod
bernardm28 bernardm28 organization(s): The University of Tennessee at Chattanooga
mr_scumbag mr_scumbag organization(s): Code Journeymen
shaal shaal volunteering organization(s): Phase2
weekbeforenext weekbeforenext organization(s): Lullabot
irina-1 irina-1
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.