Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
seantwalsh organization(s): CrowdCG
anoopjohn
bsnodgrass organization(s): net2Community, Inc.
fathershawn volunteering organization(s): Memorial Sloan Kettering Cancer Center
froboy volunteering organization(s): ImageX
gargsuchi organization(s): Salsa Digital
heatherwoz organization(s): OpenScholar
jdleonard volunteering organization(s): Modern Biz Consulting
kthull organization(s): Blue Drop Shop
leslieg organization(s): Redfin Solutions, LLC
mandclu volunteering organization(s): Acquia
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
megan_m organization(s): Woolwich Web Works
mharrell
paulmckibben organization(s): Turbojet Technologies
philalonso volunteering
RAhul
volkswagenchick volunteering
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.