Contribution records
Contributors

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

Give credit to everyone
xmacinfo xmacinfo organization(s): xMac info
l8518 l8518
scareyclott scareyclott
seenafallah seenafallah
joelpittet joelpittet volunteering organization(s): The University of British Columbia
GilAnder GilAnder
guruken1 guruken1
SuperTyp SuperTyp
tschewe tschewe volunteering
cozzamara cozzamara
ajoscham ajoscham
duckzland victheme
nairb nairb
japerry japerry
BartNijs BartNijs
aramboyajyan topsitemakers
damienmckenna damienmckenna organization(s): Current
mkolar martincollar volunteering
goose2000 goose2000
keypetery keypetery volunteering
mustanggb akamustang
sam452 sam452 volunteering
Egmund Egmund
pietrocap pietrocap
joseph.olstad joseph.olstad
robert gomez robert gomez
alex oliver perez alex oliver perez
vagelis-prokopiou Vagelis volunteering
k.elizabeth k.elizabeth
stephen ollman StephenOllman
chris.jichen chris.jichen
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.