Issue
Contribution records
Contributors

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

Give credit to everyone
quicksketch
alanburke
shanefjordan
marie_t
mrfelton
3cwebdev
matt2000
asak
wuf31
bwoods
k3vin
latte
gausarts
KrisBulman
internetdevels
Panda_N_Shark
grey_
sunset_bill
taxicab221
djalloway
cdale
mukatira
iNade
nelslynn
summit
zapscribbles
pebosi
attiks
marcvangend
jabraben
z33k3r
matangi
eff_shaped
goldkey266
kwon
VladoMire
excaliburst
rzelnik
jtchan
amariotti
diederik_2mpact
ianchan
ldweeks
cameronp
wolftmc
dtarc
joachim
roknrod12
Rupert3
meshweta
itangalo
paskainos
lsolesen
hendrohwibowo
thomasmurphy
vrwired
Chris Charlton
Jim Ruby
amir simantov
ramandeep.kaur
danny englander
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.