Contribution records
Contributors

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

Give credit to everyone
davidwbarratt davidwbarratt
robloach robloach
seldaek seldaek
cosmicdreams cosmicdreams
catch catch
ParisLiakos rootatwc
patcon patcon
mile23 Mile23
xjm xjm
alexpott alexpott
sun sun
jameshalsall jameshalsall
mgifford mgifford
mradcliffe mradcliffe
tstoeckler tstoeckler
nicholasruunu nicholasruunu
bojanz bojanz
fabianx Fabianx
martin107 martin107
eclipsegc eclipsegc
donquixote donquixote
daffie daffie
chx chx
adammalone typhonius
dawehner dereine
webchick webchick
effulgentsia effulgentsia
hussainweb hussainweb
plach plach
dww dww volunteering
greg.1.anderson greg1anderson
moshe weitzman weitzman
Jeff Burnz jmburnz
tim.plunkett tim.plunkett
i.bajrai i.bajrai
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.