Contribution records
Contributors

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

Give credit to everyone
dww dww
ksenzee ksenzee
David_Rothstein drothstein
BenK benk
JohnnyX JohnnyX
joachim joachim
NathanM NathanM
dpi dpi
ericc3 ericc3
kiphaas7 Kiphaas7
bldskl bldskl
mariomc mariomc
wmnnd wmnnd
ccrackerjack ccrackerjack
kinshuksunil kinshuksunil
RealBirkoff RealBirkoff
rcross rcross
nicktech nicktech
achton achton
kclarkson kclarkson
greggles greggles
webankit babbar.ankit
chapabu chapabu
Anticosti Anticosti
bnl bnl
rolfmeijer rolfmeijer
marksiebert marksiebert
yurtboy yurtboy
sklgromek sklgromek
Gr3fweN Gr3fweN
btmash btmash
upupax upupax
rfay rfay
ezra-g ezrag
danny englander danny-englander
jody lynn lynn
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.