Contribution records
Contributors

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

Give credit to everyone
yoroy yoroy
seutje seutje
David_Rothstein drothstein
dries dries
catch catch
int int
mcrittenden mcrittenden
ksenzee ksenzee
jeffschuler jeffschuler
ronald_istos istos
mikeytown2 mikeytown2
attiks attiks
Bojhan bojhan
jenlampton jenlampton
alexanderpas alexanderpas
sun sun
eigentor eigentor
jolos jolos
SeanBannister seanbannister
robloach robloach
amc amc
bensnyder bensnyder
JacobSingh JacobSingh
webchick webchick
v8powerage shaman
chx chx
agentrickard agentrickard
merlinofchaos merlinofchaos
cweagans cweagans
Crell Crell
rickvug rickvug
gábor hojtsy goba
te-brian BrianLink
paul.lovvik paullovvik
eclipsegc eclipsegc
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.