Issue
Contribution records
Contributors

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

Give credit to everyone
voxpelli
hefox
tomgf
merlinofchaos
rypit
johnv
dawehner
RSpliet
girishmuraly
vaartio
nicksanta
heatherwoz
giorgio79
mototribe
slashrsm
alesr
johnnydarkko
kenrbnsn
ygerasimov
Jaza
johnshortess
incaic
merilainen
gustavol
mrded
bgm
rogierbom
freezypop
b2f
jcisio
BrockBoland
greggles
agentrickard
hailu
essenceofginger
rafaqz
barwonhack
pjcdawkins
harrrrrrr
rbennion
kevinquillen
duaelfr
milton_segretti
Exploratus
erald
catch
drumm
hhschoone
citlacom
el1_1el
zipymonkey
azinck
jthorson
dokumori
tvn
david_garcia
blackandcode
grasmash
killua99
jphil
lmeurs
sp_key
digitalfrontiersmedia
user654
tim.plunkett
dmitriy.trt
de-fa
greg boggs
Lux Delux
Renee S
geek-merlin
Quyen bui
Désiré
Chris Charlton 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.