Contribution records
Contributors

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

Give credit to everyone
catch catch
dries dries
BarisW barisw
swentel swentel
jschumann jschumann
davyvdb davyvandenbremt
BassistJimmyJam bassistjimmyjam
webchick webchick
mcrittenden mcrittenden
webkenny webkenny
fending fending
fgm fgm
eaton eaton
chx chx
Stalski stalski
alexjarvis alexjarvis
sun sun
yoroy yoroy
Bojhan bojhan
jrabeemer Giovanni_Glass
Crell Crell
pwolanin pwolanin
fago fago
andypost andypost
colan colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
lpalgarvio LPCA
bojanz bojanz
gmak gmak
robloach robloach
David_Rothstein drothstein
xjm xjm
msonnabaum msonnabaum
skottler skottler
klonos klonos
aspilicious aspilicious
geerlingguy geerlingguy
dalra dalra
greg.harvey greg.harvey
dave reid davereid
lars toomre ltoomre
Tor Arne Thune torthu
chris matthews ChrisMatthews
Git commit message
Commit types
  • 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

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.