Contribution records
Contributors

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

Give credit to everyone
mstef mikestefff
seanmrafferty seanmrafferty
safshar safshar
kmoll kmoll
heger245 heger245
khoatm mkchen
geoffreyr geoffreyr
cilefen cilefen
mustanggb akamustang
firewaller firewaller
robertom robertom organization(s): bmeme
willzyx willzyx
joelpittet joelpittet organization(s): The University of British Columbia
narkoff narkoff
damienmckenna damienmckenna organization(s): Current
danny englander danny-englander
glass.dimly glassdimly
zalak.addweb sipra.patra
j.b j.b
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.