Issue
Contribution records
Contributors

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

Give credit to everyone
franz
jonmcl
rolodmonkey
littledynamo
g089h515r806
sin
twistor
crystaldawn
johnv
sdrycroft
dobe
hairqles
moelius
megachriz
lmeurs
brandonc503
eelkeblok organization(s): Dutch Open Projects
mikran organization(s): Mediamaisteri Oy
joseAyudarte91
AgentJay
dflitner
alex72rm
jimmynash
darksnow
rkelbel48
trentl
stred
cmarcera
jandewit6
arnoldbird
blazindrop
CLEE25
honza pobořil
F.G
nicholas.alipaz
adrien.felipe
omar alahmed
alex.cunha
michel.settembrino organization(s): European Commission and European Union Institutions, Agencies and Bodies
STNyborg
bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
Git commit message
Commit types
  • 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

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.