Issue
Contribution records
Contributors

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

Give credit to everyone
ownage
froboy
franz
johnbarclay
dman
smitty
nielsonm
rtdean93
colan
xlyz
emackn
Niremizov
madeby
cdmo
bnine
gaele
liquidcms
jjclint
millaraj
twistor
mksweet
merilainen
cthiebault
akosipax
guillaumev
mikran
uhkis organization(s): Mediamaisteri Oy
vaccinemedia
johnv
kingandy
gapa
ditcheva
Michsk
mbatterton
littledynamo
manuelBS
mparker17
blueblot
megachriz
summit
loker
hcethatsme
killua99
sin
Mykolas
chrowe
coredumperror
gcb organization(s): ThinkShout
nickmaine
Exploratus
Nux
Leeteq
OnkelTem
sonicthoughts volunteering
apmsooner
jomarocas volunteering
troybthompson
mikemccaffrey organization(s): ThinkShout
demonde
vbard
Niklas Fiekas
shiraz dindar
lunk rat
wuinfo - bill wu
a.ross
ArtActivator.com
christo snyman
morbus iff
jptl
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.