Issue
Contribution records
Contributors

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

Give credit to everyone
mrmeech
rickharington
dwkitchen
funature
merilainen
logaritmisk
TelFiRE
kyletaylored
jibran
pierrelord
stupiddingo
nyleve101
btopro
deg
jpitassi
CarlosML
bradallenfisher
dddave
miik4
capellic
xaqrox
metastate
nuncius
mohamadaliakbari
dixon_
rteijeiro
heddn
Mavro
bwoods
Geizt
MHz
alesel
pacome
xaa
spkrs
kopeboy
zanix
likewhoa
newme154
TheRealDeal
guschilds organization(s): Chromatic
stevieb
2pha
knalstaaf
alexit873
errand
sam152 volunteering organization(s): PreviousNext
szeidler organization(s): Ramsalt Lab
shaneonabike
vinoth.3v
andrew smith
charlie charles
Andre-B
morleman@gmail.com
dom.
honza pobořil volunteering
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.