Contribution records
Contributors

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

Give credit to everyone
arnoldbird arnoldbird
cilefen cilefen volunteering
denutkarsh utkarsh-dixit organization(s): Google Code-In
bhatrafiq bhatrafiq
yzan yzan
kswamy KalaiselvanSwamy volunteering
ktch_my ktch_my
SylDanh SylDanh
matt_paz mattpaz
rfletcher73 rfletcher73 volunteering
docans docans volunteering
justinmello32 justinmello32 volunteering
phthlaap phthlaap volunteering
chenx319 chenx319
egfguedes egfguedes
jhnnsbstnbch jhnnsbstnbch
mark_fullmer markfullmer
sagir42 sagir42
jhodgdon jhodgdon
quietone quietone organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
Abhilash001 Abhilash001
seppe beelprez SeppeBeelprez
liam morland lkmorlan organization(s): University of Waterloo
Hong Cai Hong Cai volunteering
karthikeyan gandhimathinathan karthikeyan gandhimathinathan
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.