Contribution records
Draft
Contributors

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

Give credit to everyone
walker6o9 walker6o9
mikey_p mikey_p
crea crea
jvieille jvieille
effulgentsia effulgentsia
Rhino Rhino
Poieo Poieo
andrewspringman andrewspringman
ionz149 ionz149
ikeigenwijs Leopard_Solutions
hnln HnLn
damienmckenna damienmckenna
mbasfour M.B.Asfoor
josephcheek cheekdotcom
patkai belapatkai
alippai alippai
matts777 matts777
achton achton
imclean imclean
jpklein jpklein
alduya alduya
bleen bleen18
pragna pragna
karibel morybel
vmevada102 vmevada102
shiraz dindar Shiraz
charlie-s csdco
dijusam dijusam
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.