Contribution records
Contributors

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

Give credit to everyone
Remon rgeorgy
benone benone
runzipel runzipel
scotjam scotjam
jthomasbailey jthomasbailey
vlooivlerke vlooivlerke_git
technikh nikhildubbaka
mr_wookie mr_wookie
carlitus carlitus
funature funature
jcohlmeyer jcohlmeyer
maharag maharag
ptmkenny ptmkenny
marcelsafont marcelsafont
hadsie hadsie
josebrito josebrito
whop whop
martijn houtman MartijnHoutman
Berliner-dupe Berliner-dupe
Barry Tielkes Barry_Tielkes
honza pobořil bobik volunteering
emdash emdash
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.