Contribution records
Draft
Contributors

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

Give credit to everyone
moonray moonray organization(s): Chapter Three (acquired by Kanopi Studios)
dzinkevich dzinkevich organization(s): Zivtech
jonathanshaw jonathanjfshaw
berdir berdir organization(s): MD Systems GmbH
csedax90 CRY_X2
nghai nghai
rooby rooby
gambry gambry organization(s): manifesto
xano Xano organization(s): Druid customer(s): Lääkärikeskus Aava Oy
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
handkerchief handkerchief
cola ucola
mxh hauptm volunteering organization(s): Hubert Burda Media
sleepingmonk sleepingmonk volunteering
blazey blazey organization(s): Amazee Labs
prineshazar PrineShazar
boby_ui boby_ui volunteering
pfrenssen pfrenssen
catch catch organization(s): Third and Grove
jurgenhaas jurgenhaas organization(s): LakeDrops
dalin dalin organization(s): Four Kitchens
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
moshe weitzman weitzman 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.