Contribution records
Contributors

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

Give credit to everyone
dkruglyak dkruglyak
jeremy Jeremy
chx chx
dopry dopry
dries dries
dgrant dgrant
Marandb Marandb
yongrokc yongrokc
njehlen njehlen
insomoz insomoz
asb asb
klance klance
jasonwhat jasonwhat
RobRoy robroy
kc kc
pamphile pamphile
nathandigriz nathandigriz
mediafrenzy mediafrenzy
eurokate eurokate
bradlis7 bradlis7
xeeya xeeya
beginner augustin
magico magico
Adrian Freed adrianfreed
matt westgate mathias
moshe weitzman weitzman
Bill St. Clair billstclair
venkat-rk venkatrk
Stefan Nagtegaal Stefan Nagtegaal
tng@neuralgourmet.com tng@neuralgourmet.com
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.