Issue
Contribution records
Contributors

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

Give credit to everyone
mcaden
supportPIC
derjochenmeyer organization(s): forward-media.de
BenK
jjchinquist
steinmb
ccardea
lloydpearsoniv
mile23
jherencia
larowlan
summit
mototribe
vhwouter
phayes
TravisJohnston
pcbudde
jorditr
kvit
heddn
mtoscano
dinarcon organization(s): Agaric
mikefyfer
giufog
platinum1
malcomio
hanoii
panhead490
jeppy64
lias
imclean organization(s): Digital Ink
christianadamski volunteering
alan d.
Adam S
jm.federico
andrea.cavattoni
brandy.brown
Sinan Erdem
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.