Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dpi volunteering
acbramley organization(s): PreviousNext customer(s): Service NSW
komlenic
jastraat organization(s): CivicActions, Technivant customer(s): Centers for Medicare and Medicaid Services
randalv
maacl
kriboogh organization(s): Calibrate
amanire organization(s): Environmental Defense Fund
akalam
kmonty organization(s): BKJ Digital
dripa organization(s): DICTU
goldin
larowlan organization(s): PreviousNext
johnpitcairn
ammaletu
fenstrat volunteering organization(s): PlexityNet
chrisgross
joao sausen organization(s): Dexa
liam morland organization(s): University of Waterloo
luke.leber
ian.ssu organization(s): Sonoma State University
erik.erskine organization(s): Annertech
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.