Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
teknorah organization(s): tekNorah customer(s): BLUEFLY.IO LLC, MidCamp
ahughes3 volunteering organization(s): Lullabot
alentino volunteering organization(s): Sandstorm
andrewozone organization(s): Principal Financial Group
ao5357 volunteering
brianperry
camoa organization(s): Palcera
dandaman volunteering
dorficus organization(s): HeroDevs
garphy organization(s): Evolving Web
gauravmishra7 organization(s): Material
irinaz volunteering organization(s): Fibonacci Web Studio
jwineichen organization(s): Madison Public Library
katannshaw organization(s): Lullabot
keepersmith organization(s): Sandstorm
keiserjb
mandclu volunteering organization(s): Acquia
mikemiles86 organization(s): MIT Sloan
mlncn organization(s): Agaric customer(s): Drutopia
ninelivesblackcat volunteering organization(s): NLBC Works
rklawson organization(s): Evolving Web
rlhawk organization(s): Slalom
starshaped organization(s): Lullabot
ultimike organization(s): DrupalEasy
volkswagenchick volunteering
dries
fmitchell organization(s): Bright Plum, Inc.
markie organization(s): Interpersonal Frequency
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.