Contribution records
Contributors

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

Give credit to everyone
Frando frando
ksenzee ksenzee
eigentor eigentor
kiphaas7 Kiphaas7
shunting shunting
EmanueleQuinto EmanueleQuinto
alexanderpas alexanderpas
David_Rothstein drothstein
Bojhan bojhan
catch catch
amc amc_git
servantleader servantleader
Annakan Annakan
scroogie scroogie
jrabeemer Giovanni_Glass
EvanDonovan evandonovan
drewish drewish
nvahalik nvahalik
HedgeMage HedgeMage
JayNL JayNL
yesct YesCT
casey casey
cwgordon7 cwgordon7
yoroy yoroy
dhrosa dhrosa
dries dries
marcingy marcingy
mustanggb akamustang
attiks attiks
mlncn mlncn
webchick webchick
effulgentsia effulgentsia
cosmicdreams cosmicdreams
geerlingguy geerlingguy
xjm xjm
dcmistry dcmistry
bleen bleen18
yashadev yasha
piyuesh23 piyuesh23
nod_ nod_
alex ua alexua
te-brian BrianLink
sun.core sun.core
Everett Zufelt everettz
dharmendra.jadeja dharmendra-jadeja
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.