pillarjs.github.io

Question

pillarjs.github.io

Opened this issue 10 years ago · 8 comments

renamed this repo to discussions and forked badgeboard to pillarjs. realized afterwards that i could've just pulled from badgeboard, but whatever. nice to have "forked from" at the top left.

there's no need to migrate issues just yet, but we should open new ones in pillarjs.github.io like we do with jshttp and eventually delete this repo

Answer 1 · 2014-08-29T04:37:37.000Z

one thing to note about forked repos: all commits to a forked repo that are not merged back into the original repo do not count in your contributions graph on your profile page in github :)

Answer 2 · 2014-08-29T04:42:24.000Z

that's one reason why i like forks haha make me look less like a maniac

Answer 3 · 2014-08-29T04:44:46.000Z

i like the badgeboard forking mainly because you can go to the badgeboard github and view the "network" to see everyone who is using badgeboard, actually.

Answer 4 · 2014-08-29T07:17:51.000Z

and view the "network" to see everyone who is using badgeboard

And also everybody who forked badgeboard, made pull request and forgot it ever existed.

Looking at joyent/node for example, I doubt people have 7068 different versions of it. :)

Answer 5 · 2014-08-29T07:19:29.000Z

@jonathanong , now we have two repos for discussions, that's confusing.

Answer 6 · 2014-08-29T07:26:24.000Z

migrate to the other one.

Answer 7 · 2014-08-29T07:27:54.000Z

same thing for jshttp to get "forked from" thingy?

Answer 8 · 2014-08-29T07:28:55.000Z

meh i don't think it's worth it since we have so many issues and custom stuff already