Contribution records
Draft
Contributors

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

Give credit to everyone
TJM TJM
dczepierga dczepierga
alalamo TainoTechy
ju1i3 ju1i3
harri00413 harri00413
mkesicki michal_cksource
wwalc wwalc
tdryden tdryden
eduuser eduuser
totap totap
MarkRennes MarkRennes
pixelsnap pixelsnap
mandirao mandirao
cheshire137 cheshire137
fehin fehin
misscosmic misscosmic
nnhaswell nnhaswell
vanderb vanderb
Vulcan Vulcan
Misange Misange
vrivera82 vrivera82
ikeigenwijs Leopard_Solutions
cburyta cburyta
thekurt thekurt
jettero jettero
andyb5051 andyb5051
ressa ressa
Gemini Lights Gemini_Lights
Fiable.biz Fiable.biz
luke xi justinking
Tux Love Tux_Love
hisham.malik hisham.malik
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.