Issue
Contribution records
Contributors

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

Give credit to everyone
karens
yched
robloach
rickvug
greggles
psicomante
catch
misty3
jrabeemer
murz
cfennell
trungdong
cabbiepete
harriska2
jmarki
yojoe
tormu
ronald_istos
ximo
freakx0
rayarub
aozuas
CosmicVoyager
jystewart
rudegrrl401
arturpl
dellis
fm
karenm
wayland76
mrgoltra
udienz
konsumer
JMowery
gellpak
Soulhuntre
Domodel
scottrigby
tomski777
jpewert
sfranchi
kkkkkkkkkkkkkkkkkkkkkkk
stevenpatz
encho
disterics
pjb
wuf31
Freso
huayen
plexato
zilla
brianV
gerritvanaaken
Roxpace
hatsch
schuyler1d
Otaci
idflorin
jaredm
duckpuppy
crsneil
waby
jeffvogelsang
phano
ogi
amy_cgi
rvk
creamyhorror
jrglasgow
dmurphy
redben
changed
flickerfly
corcken
paperfield
DanBollinger
cjeich
drewish
rjleigh
prbass
cwagar
bobman83
mikeque
madone
na3s
sun
priyanka07
steveeq
Wolfflow
moshe weitzman
s.daniel
Island Usurper
Beau Gunderson
aren cambre
zach harkey
Antoine Lafontaine
Ryan Palmer
Florian R
robin monks
Chris Bray
Slim Pickens
wim leers
hass
Git commit message
Commit types
  • 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

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.