Contribution records
Contributors

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

Give credit to everyone
dawehner dereine volunteering
nod_ nod_ volunteering
olli olli
larowlan larowlan organization(s): PreviousNext customer(s): amaysim Australia Ltd.
lewisnyman lewisnyman
Jalandhar Jalandhar
rpayanm rpayanm
jhedstrom jhedstrom organization(s): Phase2
berdir berdir organization(s): MD Systems GmbH
mrjmd mrjmd
s_leu s_leu organization(s): MD Systems GmbH
sasanikolic sasanikolic organization(s): MD Systems GmbH
joelpittet joelpittet volunteering
maijs maijs organization(s): Mearra (formerly known as Wunder)
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
wim leers wimleers
trupti bhosale Truptii organization(s): Axelerant
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.