Contribution records
Contributors

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

Give credit to everyone
mikeytown2 mikeytown2
David_Rothstein drothstein volunteering
oadaeh oadaeh organization(s): Hook 42
sjerdo sjerdo volunteering
anrikun anrikun
gbirch gbirch volunteering organization(s): Tech-Tamer, LLC
mustanggb akamustang
collinhaines collinhaines
izmeez izmeez
tr tr
mcdruid mcdruid organization(s): Acquia
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
aerozeppelin aerozeppelin
alexpott alexpott organization(s): Thunder
gapple gapple volunteering
gnuget gnuget volunteering
johns996 johns996
mgifford mgifford
joseph.olstad joseph.olstad
liam morland lkmorlan organization(s): University of Waterloo
hass hass
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.