Contribution records
Contributors

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

Give credit to everyone
Shmee Shmee
victory17 victory17
stoltoguzzi stoltoguzzi
agerson agerson
dwalker51 dwalker51
gkazhus gkazhus
Starminder Starminder
RedTop RedTop
avizzino avizzino
boonejeeper boonejeeper
David_Rothstein drothstein
theapi PeterC
dartdev DartDev
kifuzzy kifuzzy
parsingphase parsingphase
TripX TripX
flightrisk flightrisk
Cogito Cogito
esculcar esculcar
chriz001 chriz001
brodiebrodie brodiebrodie
mhamed mhamed
dadou351 dadou351
mcfilms mcfilms
jgraham jgraham
aftab0000 aftab0000
lsolesen lsolesen
Taxoman Taxoman
ddarras2012 ddarras2012 volunteering
hanksterr7 hanksterr7 volunteering
ivnish ivnish
rob c robc
Dinesh Kumar Sarangapani DineshKumar
chaloum edmedia
Joenet-dupe Joenet
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.