Contribution records
Contributors

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

Give credit to everyone
plach plach
light9 light9
Leeteq Leeteq
realOFF realOFF
kkretsch kkretsch
dagmar dagmar
cburschka arancaytar
jandd jandd
lilou lilou
catch catch
altavis altavis
momper momper
giorgosk GiorgosK
talino talino
arhak arhak
marcushenningsen marcushenningsen
koorneef koorneef
sinasalek sinasalek
ckidow CKIDOW
fuerst fuerst
heine heine
andypost andypost
Yas375 yas375
webchick webchick
nonsie nonsie
ducdebreme ducdebreme
Michsk Lasac
Bilmar Bilmar
clashar clashar
janhajk janhajk
ninebark ninebark
Loquere Loquere
oriol_e9g oriole9g
David Koudela David Koudela
agence web coheractio CoherActio
Frank Steiner Frank Steiner
ball.in.th ballinth
gábor hojtsy goba
W.M. Geir19
mafi-a mafi-a
claudiu.cristea claudiucristea
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.