Issue
Contribution records
Contributors

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

Give credit to everyone
vm
ken54671
drupov
jacerider
merlinofchaos
rtackett
chadd
perfectdream
askit
dagmar
vancip
junro
bryrock
talino
halver
zengenuity
izmeez
MantasK
aharown07
miraclestyle
ajayg
deviantintegral
agentrickard
tobey_p
leoklein
rfay
mikeytown2
dawehner
igorik
crea
johnpitcairn
dleong
q0rban
MarnitaM
ray17n
kompatv
attilahooper
rhysemt
logii
drupal92037
ycimlynn
Pasi
boobaa
TechnoBuddhist
advseb
rewe
sgregory
bonvga
kyle_mathews
Tarsjusz
bbc
samchok
jannalexx
MatthijsG
pixlkat
MatteNoob
tchurch
ambo
peterbissonnette
CardinalFang
strauch
bartezz
scroogie
Leeteq
kesmeby
Crell
Tim_O
ryivhnn
RobinLayfield
shadysamir
Sinan Erdem
Frank Steiner
steven jones
Parkes Design
damien tournoud
node-nine_inc.
snorkers
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.