Issue
Contribution records
Contributors

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

Give credit to everyone
merlinofchaos
Firetracker
Kripsy
daneyuleb
bvienneau
seddonym
JoeMcGuire
netbear
yang_yi_cn
martysteer
sbydrupal
gbrussel
davidneedham
SeanBannister
lelizondo
guysung
socialnicheguru
ncameron
egbertb
czeky
netentropy
giorgosk
yugene
nyleve101
dagmar
rpeters
cliffordx
canishk
frankie_2304
giorgio79
saratt
tustind
lmaharas
burgs
milehighlife
operations
dawehner
joyseeker
summit
web2get
ressa
tribe_of_dan
dzaus
thomaslucas
rajmataj
awasson
fehin
mxt
hwasem
dadderley
makkon
trgreen17
adityamenon
moonshdw8
jeuelc
zmove
gmaximus
supriyarajgopal
mustanggb
El Bandito
Marko B
robby.smith
joachim desarmenien
Jānis Bebrītis
jeff.maes
sashi.kiran
ctuxboy
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.