Issue
Contribution records
Contributors

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

Give credit to everyone
mlncn volunteering organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
catch organization(s): Third and Grove
ronbot
quietone organization(s): PreviousNext
atowl volunteering
ben_a
jimmycann
lan
nterbogt customer(s): Department of Customer Service, NSW
silverham organization(s): EY Digital
tarawij organization(s): govCMS (Australian Government Department of Finance)
tyrellblackburn
yi_jiang volunteering
dcam organization(s): USDA-ARS
vensires organization(s): E-Sepia Web Innovation
smustgrave organization(s): Mobomo
kim.pepper organization(s): PreviousNext
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.