Issue
Contribution records
Contributors

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

Give credit to everyone
alberto56
bserem
eelkeblok
duaelfr organization(s): Happyculture
dawehner organization(s): Cando
PascalAnimateur
bendev
mpotter organization(s): Phase2
BarisW organization(s): ronder
rodrigoaguilera volunteering
megachriz organization(s): WebCoo
anrikun
kevinn
tanmoy1981 volunteering
hanoii
Jeroen_005 organization(s): Pàu
grimreaper volunteering
scuba_fly organization(s): ronder
dbazuin organization(s): ronder
fuzzy76
das-peter
michel.settembrino organization(s): Colruyt Group Services, MS-Informatique
nico.knaepen 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.