Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
gnucifer
sunyu0072007
JvE organization(s): iO, One Shoe
arcane
bojanz
johnpitcairn
chriscohen
teezee
awm
David_Rothstein
amitaibu
joachim
kevinob11
sw3b
olofbokedal
damienmckenna
kostajh
socialnicheguru
inghamn
jojonaloha
podarok
partdigital
fullerja
lpeabody
hideaway
quotesbro
azinck
ndobromirov
anybody volunteering
jonathanshaw
eelkeblok organization(s): iO
sdsheridan
bburg organization(s): Forum One
spotzero organization(s): Coldfront Labs Inc.
imiksu organization(s): Mearra (formerly known as Wunder)
handkerchief
damien tournoud
pravin.katragadda
lisa.rae
elephant.jim
imre.horjan
dave reid
alina.basarabeanu
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.