Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dawehner
rogical
merlinofchaos
arski
m3n0R
jsacksick
MichaelCole
develpr
sgb9809
areikiera
bryancasler
dagmar
elly
dasjo
igget76
rodp
sergeysynergy
rutcreate
Slacky08
oresh
damiankloip
bdone
olli
giorgio79
jibran
alexpott
mxt
aaronbauman organization(s): Message Agency
Woodyjon
yesct
daveramps
technikh
schifazl
OnkelTem
brightbold
nithinkolekar
osopolar
mustanggb
isimgt
greggadsdon organization(s): ComputerMinds
damienmckenna organization(s): Current
tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
chuck_theobald
randell volunteering
skylord
tim.plunkett
ankit.goyal5
dizi.joao
milos.kroulik
sachin.bansal
eric.chenchao
chris matthews volunteering
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.