Issue
Contribution records
Contributors

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

Give credit to everyone
loze
ainigma32
jcnventura
peacog
ao2
markus_petrux
samuele
gerritvanaaken
shelleyp
jgadrow
design4effect
rzelnik
jantoine
rlmaltais
naxoc
asak
ianchan
summit
sreynen
hedac
kimblim
Nagyman
MatthieuP
mattiasj
gollyg
hendrinx
d3zign7reak
mcrittenden
brianmercer
sartogo
laja
denis_sle
System6Hosting
antiorario
ayalon
verikami
sobi3ch
fax8
achton
perusio
intyms
pwolanin
davidwhthomas
guypaddock
Kutakizukari
bleen
hellaswebnews
dtsio
dragan_r
hillaevium
psynaptic
stemount
momper
damienmckenna
TD912
mattwfx
anujahiniduma
adamcadot
kndr
tomass_zutis
benschaaf
lizac
rosshj
arjun0819
ReKoNe
Eduart
chinita7
janton
jelo
aaronmeister
mheinke
RytoEX
geerlingguy
damien tournoud
gábor hojtsy
robert-hartl
danny englander
codepeak-1
nedim.hadzimahmutovic
iamfil
hass
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.