Issue
Contribution records
Contributors

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

Give credit to everyone
Thew organization(s): Google Code-In
mgifford organization(s): OpenConcept Consulting Inc., CivicActions
lstrange
andrewmacpherson volunteering
amanire volunteering organization(s): Isovera
jontynewman
jacine organization(s): Chapter Three (acquired by Kanopi Studios)
tanubansal organization(s): Salsa Digital
lauriii
codebymikey organization(s): Zodiac Media
kalpaitch volunteering
solideogloria
jldust organization(s): Aten Design Group
dcam volunteering organization(s): USDA-ARS
liam morland organization(s): OpenPlus, Scouting Waterloo Region
smustgrave organization(s): Mobomo
catch organization(s): Third and Grove
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.