Contribution records
Contributors

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

Give credit to everyone
bdragon bdragon
uprojects uprojects
yesct YesCT
monjohn monjohn
mrgoltra mrgoltra
izmeez izmeez
sagannotcarl sagannotcarl
pursuitofliberty pursuitofliberty
damienmckenna damienmckenna
cpall cgp
sfyn sfyn
BartVB BartVB
nodecode nodecode
nickl nickl
rubymuse rubymuse
pnee pnee
kpojeta kpojeta
kreynen kreynen
mfb mfb
srobert72 srobert72
piepkrak piepkrak
BenK benk
osirisioux osirisioux
fabianderijk fabianderijk
greenskunk GreenSkunk
JayCally JayCally
pol Pol
joelstein joelstein
jghyde jghyde
nchase nchase
giorgosk GiorgosK
twooten twooten
ankur ankur
roball roball
bryancasler animelion
Chris Przybycien chrisprzybycien
shane birley shanebirley
La M La M
Nick Robillard nickel
smk-ka smk-ka
zoltán balogh zlyware
john.money gestaltware
michaelfavia michaelfavia
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.