Contribution records
Draft
Contributors

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

Give credit to everyone
mariuss mariuss
catch catch
ahoeben ahoeben
xjm xjm
rays rays
alexandreracine alexandreracine
Crimson Crimson
codepoet codepoet
edoc edoc
KeithDaniels KeithDaniels
l8a l8a
junyor junyor
coltrane coltrane
adam640kb adam640kb
amnion amnion
floretan floretan
Cool_Goose Cool_Goose
maartenvg maartenvg
dmagre dmagre
redaccion redaccion
jpoesen jpoesen
momper momper
CompShack CompShack
sdecabooter sdecabooter
macgirvin macgirvin
nedjo nedjo
dmitrig01 dmitrig01
andyceo andyceo
dries dries
pozdneev pozdneev
smandal smandal
frames frames
arhak arhak
nancydru nancyw
kaztur kaztur
andypost andypost volunteering organization(s): Skilld
Camus-1 Camus-1
aleksey.tk cyberpunk
gábor hojtsy goba
keith.smith keithsmith
robin monks robinmonks
smustgrave smustgrave organization(s): Mobomo
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.