Contribution records
Contributors

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

Give credit to everyone
nod_ nod_
jgtrescazes jgtrescazes
tstoeckler tstoeckler
fietserwin fietserwin
sun sun
cweagans cweagans
seanr seanr
BrockBoland brockboland
Atomox Atomox
seutje seutje
onelittleant onelittleant
ergophobe ergophobe
mgifford mgifford
tvn tvn
yesct YesCT
danylevskyi danylevskyi
heine heine
David_Rothstein drothstein volunteering
heddn lucashedding
Georgique Georgique
pgandul pgandul
geertvd geertvd organization(s): XIO
quicksketch quicksketch organization(s): Lullabot customer(s): Carnegie Mellon University
dmitriy.trt dmitriytrt
stefan.r stefan.r
lachezar.valchev graphityx
bogdan khrupa bogdan khrupa
eric.chenchao cityreader
rahul.shinde rahul_shinde
hass hass
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.