Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
joachim
pbo
chx
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
dema502
akoepke
semanthis
tordeu
remaye
dasjo
warmth
developerweeks
dydave
dbehrman
derhasi
windmaomao
robertwb
mpgeek organization(s): Phase2
pschuelke
danharper
killua99
rosk0
balazswmann
willowdigit
dillix
technikh
euk
jgullstr
osopolar
nithinkolekar
damiankloip
mvlabat volunteering
mustanggb
lionguard volunteering
bryanmanalo volunteering
eric_a
jiv_e organization(s): LilDrop Consulting
shi99
drclaw
damienmckenna organization(s): Current
davemaxg
skylord
thetwentyseven
kristofferwiklund organization(s): Websystem
ankithashetty volunteering organization(s): Specbee
Collins405
eott
pmglondon volunteering
tim.plunkett
tim.abbott
scott.whittaker volunteering
maciej.zgadzaj
chris matthews volunteering
davidwhthomas
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.