4 ms·

I know he gave credit in the README, but why does this ~30 line shell script need its own repo? Seems more like a cheap grab for Github Stars rather than to pro

• paulirish 11y ago
  A bit ago, I had indicated this script should be more accessible than copying two separate files out of my dotfiles repo: https://github.com/paulirish/dotfiles/blob/master/bin/diff-so-fancy#L34 https://github.com/paulirish/dotfiles/blob/master/bin/diff-s... Steve took the initiative to put this in it's own repo. Seems okay; I was being rather slow to ship it for real.
  • pierrebeaucamp 11y ago
    All good then ;)
• ceejayoz 11y ago
  Sheesh. The repo allows the stuff like installing it via `npm install -g diff-so-fancy`. It's not like a public repo costs anything, and Github stars don't get you anything either.
• stevemao 11y ago
  I think it makes it easier to add contributors. Git doesn't allow a user partially access a repo so Paul would add a few people only contributing on one script. I added some really talented contributors :) The repo under my name doesn't mean it belongs to me. In fact it belongs to the public. Everyone can contribute to it so everyone is the "owner". That's how I see open source projects. I don't mind giving it back to Paul. I did it only because I needed it. I believe a lot of people would want it more accessible too.
• jrochkind1 11y ago
  Why doesn't any code you are using need it's own repo, to track history, what does it matter how short it is?