Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
joewhitsitt organization(s): The University of Iowa
mahtab_alam organization(s): QED42
nerdstein volunteering
2pha
atul_ghate organization(s): QED42
markdorison organization(s): Chromatic
mxr576 volunteering organization(s): Pronovix
cilefen volunteering
jrockowitz volunteering organization(s): The Big Blue House, Webform module Open Collective
jonathan_hunt organization(s): Catalyst IT
scotwith1t organization(s): Riva Solutions Inc customer(s): USDA Forest Service
abhisekmazumdar volunteering
andrew.wang organization(s): Ontario Digital Service
akhil babu volunteering organization(s): QED42
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.