Issue
Contribution records
Contributors

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

Give credit to everyone
sun
effulgentsia
dkruglyak
ruloweb
danny_joris
wmostrey
intelligentdesigner
jseffel
bensnyder
twod
thekevinday
wrburgess
EliteMonk
shags_j
bryancasler
joostvdl
wOOge
shawn_smiley
chrisschaub
beyond67
loop54
zilverdistel
luckystrikerin
rwohleb
jeffschuler
jmones
cangeceiro
grossmann
Vandalf
franzkewd
tanitani
fonant
joelstein
zhangtaihao
smartango
comodo1980
mradcliffe
pdcarto
JulienD
dieuwe
anybody
derhasi
DanielF
kardave
populist
finex
idflood
summit
swentel
Stalski
adamdicarlo
baysaa
seutje
hypertext200
Ivanhoe123
ailgm
rachek
wwhurley
willieseabrook
robcarr
discipolo
afmdsouza
chriz001
xtfer
vamirbekyan
Max_Headroom
prinds
misc
orourkedd
slucero
watchdog
ayalon
lord_of_freaks
phi16181
cgutteridge
greg.harvey
ryne.andal
alex.skrypnyk
jim kirkpatrick
Juan C
andi-d
scott m. sanders
kars-t
damiancugley
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.