Issue
Contribution records
Contributors

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

Give credit to everyone
andypost volunteering organization(s): Skilld
jrb organization(s): Jay Beaton Consulting LLC
liquidcms
mrpauldriver
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): American Federation of Teachers
catch organization(s): Tag1 Consulting, Inc., Third and Grove customer(s): American Federation of Teachers
jasonluttrell
bocaj
gwenweb organization(s): WebstanZ
kurttrowbridge organization(s): Gravity Works Design + Development
crystaldawn
danchadwick
codebymikey organization(s): Zodiac Media
damienmckenna organization(s): Current
ruslan piskarov volunteering organization(s): KWALL
Sinan Erdem
thomas.wardin
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
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.