Contribution records
Contributors

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

Give credit to everyone
furamag furamag
ebremer ebremer
Shiny taniwha
robhamm robhamm
juves juves
amirtaiar amirtaiar
nihonsei nihonsei
droplet droplet
ddorian ddorian
catch catch
finex finex
marcvangend marcvangend
ecksley ecksley
gc11 gc11
AbdullahR AbdullahR
lammertsm lammertsm
mrgoltra mrgoltra
Dabitch Dabitch
bhorsa bhorsa
francisrmd francisrmd
SchwebDesign SchwebDesign
spessex spessex
zincdesign zincdesign
shortspoken moritzpeikert
rade Rade
sayansk sayansk
adamgerthel AdamGerthel
bmango bmango
jwilson3 jwilson3
drecute charyorde
Pimmy Pimmy
IronWorker IronWorker
Jamie Holly HollyIT
R2-D8 heerschlag
Greg Adams GregAdams
dave reid davereid
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.