Issue
Contribution records
Contributors

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

Give credit to everyone
dww
drewish
webchick
arhak
pillarsdotnet
mathieu
EvanDonovan
berdir
dries
cburschka
yched
brianV
johnalbin
pwolanin
AdrianB
srobert72
jannalexx
mikeytown2
danny_joris
dstol
bleen
crookednumber
febbraro
jbrauer
KerriO
calefilm
mcurry
fourmi4x
adamcadot
Wan
Shadlington
robbm
kyberman
jvinci
sonicthoughts
Chemtox
apratt
ikeigenwijs
Saoirse1916
bcobin
candelas
tr
xmacinfo
fabianx
juc1
mattcasey
alexgreyhead
raulmuroc
elc
jmuessig
lort
danepowell
dave reid
damien tournoud
Jerome F
tim.plunkett
gábor hojtsy
david.a.king
lars toomre
alexbk66-
shane birley
danny englander
greg.harvey
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.