Contribution records
Contributors

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

Give credit to everyone
kkaefer timcn
fwalch fwalch
pratyk pratyk
JirkaRybka JirkaRybka
catch catch
pancho pancho
seutje seutje
khanshakeeb msk
mxmilkiib milkmiruku
dsms dsms
thepanz thepanz
neochief neochief
alexanderpas alexanderpas
q0rban q0rban
pwolanin pwolanin
David_Rothstein drothstein
heine heine
Bojhan bojhan
sun sun
webchick webchick
coltrane coltrane
dries dries
tstoeckler tstoeckler
markus_petrux markuspetrux
clojel clojel
Georg Georg
yoroy yoroy
greggles greggles
greenreaper GreenReaper
nodecode nodecode
killes@www.drop.org killes
anders.fajerson fajerstarter
dave reid davereid
sun.core sun.core
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.