Contribution records
Contributors

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

Give credit to everyone
chx chx
sun sun
andypost andypost
webchick webchick
yhahn yhahn
beeradb beeradb
geerlingguy geerlingguy
kika kika
irakli irakli
yoroy yoroy
dries dries
leisareichelt leisareichelt
Bojhan bojhan
catch catch
joshmiller joshmiller
karschsp karschsp
David_Rothstein drothstein
emmajane emmajane
naheemsays nbz
mcrittenden mcrittenden
ica ica
linea linea
cwgordon7 cwgordon7
berdir berdir
Noyz Noyz
tstoeckler tstoeckler
Amazon Amazon
tic2000 tic2000
dmitrig01 dmitrig01
alpritt alpritt
seutje seutje
skilip skilip
babbage babbage
eigentor eigentor
mthart mthart
casey casey
Gurpartap Singh Gurpartap
gábor hojtsy goba
wretched sinner - saved by grace wretched sinner - saved by grace
moshe weitzman weitzman
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.