Issue
Contribution records
Contributors

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

Give credit to everyone
turadg
andeim
robatwork
sivaji_ganesh_jojodae
falcon
oz_an
404
nsuit
zeezhao
linuxeasy
djdevin
ratinakage
cvbuelow
ashernor
sbrousseau
barckhoff
delykj
lordpicklepuss
clarjon1
sreynen
jdvc
adrianmak
tchurch
palmereldritch
Lanbaba
kmccullagh
AndyThornton
swarad07
nirvanajyothi
vishalkhialani
scottrigby
kurti
ansim234
doxigo
digitopo
nstillblue
jeanfranco
klaasvw
j_ten_man
Madzgo
mcpuddin
pubo68
bharata
seanenroute
omvaishnav
JanderSun
drewbe121212
abhi91garg
rajatparida
Thytane
kc99
Alcaparra
maxichka
blakefrederick
ezraw
cornelism
kandrupaler
nareshbw
akalata
Renee S
aleksey.tk
christian le fournis
Hany Albeshry
diseño web palma de Mallorca
Paras Kuhad
Greg Turner
er.garg.karan
ameer mubarik bajwa
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.