Contribution records
Contributors

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

Give credit to everyone
davidmodesto davidmodesto
cutmedia cutmedia
eawheeler eawheeler
RKopacz RKopacz
zeezhao zeezhao
gubbeleye gubbeleye
umakart umakart
kubrt kubrt
matsjacobsson matsjacobsson
wOOge wooge
heykarthikwithu heykarthikwithu volunteering organization(s): Valuebound
cozzamara cozzamara
pol Pol volunteering
develcuy develCuy organization(s): Dilygent
classiccut ClassicCut
hkovacs hkovacs volunteering
roadsideok roadsideok
adrian1231 adrian_gordon
robertinop robertinop
jimafisk jimafisk
ItangSanjana iS
pslcbs pslcbs
littlethoughts littlethoughts
deanflory deanflory volunteering
alexverb Mywebmaster volunteering
carsonblack carsonblack
shane birley shanebirley
Lord Pachelbel LordPachelbel
pepe roni PepeRoni volunteering
adrien.felipe adrien.felipe
jeremy.zimmermann jeremy.zimmermann
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.