Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
teknorah organization(s): tekNorah
amazingrando organization(s): Four Kitchens
ao5357 volunteering
avento
bernardm28 volunteering organization(s): Vaultes
cneslund
ctrladel volunteering organization(s): True Summit
irinaz volunteering organization(s): Fibonacci Web Studio
jmcwherter organization(s): Gravity Works Design + Development
kurttrowbridge organization(s): Gravity Works Design + Development
lforche
maryamnmk
spandans
w01f volunteering organization(s): Timbers Dev
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.