Contribution records
Contributors

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

Give credit to everyone
michaelmol michaelmol organization(s): Immer
andrimont andrimont
aporie Aporie volunteering
aiphes aiphes
kbeck303 kbeck303 organization(s): Oomph, Inc.
rar9 Rar9
ebremner ebremner organization(s): University of Waterloo
steveoriol steveoriol
laborouge laborouge
alison alison volunteering
paperscenery paperscenery
wturrell wturrell volunteering
saschaeggi saschaeggi volunteering
solideogloria solideogloria
mr.baileys mr.baileys organization(s): SQLI - Belgium
rajab natshah RajabNatshah organization(s): Vardot
a.milkovsky milkovsky organization(s): netdoktor.at GmbH
Ralf Eisler ThomasFactory
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.