Contribution records
Contributors

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

Give credit to everyone
bojanz bojanz organization(s): Centarro
hchonov hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
aaronmchale AaronMcHale volunteering
berdir berdir organization(s): MD Systems GmbH
sakiland sakiland volunteering
anybody Anybody organization(s): DROWL.de
richgerdes richgerdes volunteering organization(s): Unleashed Technologies customer(s): Dixon Valve
taran2l Taran2L organization(s): Lemberg Solutions
ksenzee ksenzee organization(s): Smartsheet
jhuhta jhuhta organization(s): Siili Solutions
nod_ nod_ volunteering
joachim joachim organization(s): Factorial.io
pesonenv pesonenv organization(s): Siili Solutions
mmillford mmillford
helioha helioha volunteering organization(s): Unleashed Technologies
pameeela pameeela organization(s): Technocrat
godotislate godotislate volunteering organization(s): Digital Polygon
nicxvan nicxvan organization(s): nLightened Development LLC
tr tr
johnpitcairn johnpitcairn
quietone quietone organization(s): PreviousNext
catch catch organization(s): Third and Grove
julien.sibi julien.sibi volunteering
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.