Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
pierrepaul
IWasBornToWin
davidkarlsson
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
minnur
srgk
sjf
lpalgarvio
LTech
dshields
estoyausente
yazzbe
cwightrun
Dentorat
azuledu
perhenrik
WilliamV
stanly64
geresy
nielsonm
edgar971
acoral
wolf_22
rafiqasad
phily
anybody
bocaj
Thremulant
maxplus
Codeblind
thtas
tmedlen
lendude organization(s): Noctilaris
stijnstroobants
mustanggb
strelkovandreyvalerievich
dalin volunteering organization(s): Advomatic customer(s): American Federation of Teachers
zhenjan
cadoughe
ahughes3
laurajeans volunteering
nico.knaepen organization(s): Logic in Motion
zalak.addweb
sense-design
chris matthews volunteering
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.