Contribution records
Contributors

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

Give credit to everyone
timonweb timonweb
sammys sammys
gilsbert gilsbert
user654 user654
lahode lahode
hypertext200 heshanlk
gremy gremy
ruloweb ruloweb
mottihoresh mottihoresh volunteering
biblos biblos volunteering
robloach robloach organization(s): Kalamuna
dobe dobe volunteering
spadxiii SpadXIII organization(s): ezCompany
anrikun anrikun
karlshea KarlShea organization(s): Karl Shea
ciss ciss organization(s): yousign GmbH
patoshi duckx
rudiedirkx rudiedirkx volunteering
detroz detroz
veronicaseveryn veronicaSeveryn organization(s): Inclind Inc
anas_maw Anas_maw organization(s): Coders Enterprise Web & Mobile Solutions
das-peter daspeter organization(s): Cando
damien tournoud damz
drunken monkey drunkenmonkey volunteering customer(s): Sunlime Web Innovations GmbH
jason.fisher jason.fisher
nikolay shapovalov zniki.ru organization(s): RaDon
patrick r. PatrickR organization(s): UEBERBIT GmbH
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.