Contribution records
Contributors

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

Give credit to everyone
cilefen cilefen
marcoscano marcoscano organization(s): MD Systems GmbH
paulpopus paulpopus volunteering
johnchque yongt9412 organization(s): MD Systems GmbH
alonaoneill AlonaOneill organization(s): Hook 42
vacho vacho organization(s): Skilld
yogeshmpawar yogeshmpawar volunteering organization(s): QED42
volkerk volkerk organization(s): Thunder
longwave longwave organization(s): Full Fat Things
mac501 mac501 organization(s): NDP
avpaderno avpaderno volunteering
a.hover a.hover organization(s): CTI Digital
anybody Anybody organization(s): DROWL.de
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.