Why is this repo a fork?

Question

Why is this repo a fork?

sheabunge opened this issue 12 years ago · 7 comments

Why is this repo a fork of the original css-social-buttons repository instead of a separate one? You're not ever going to merge this with the original repo, are you? It also means that I can't form both yours and @SamCollins repo to the same account

Answer 1 · 2013-02-22T16:13:37.000Z

I've planned to keep it as a fork because of the fonts mainly, so I wouldn't need to copy & paste them manually. The same applies to the demo page :)

Answer 2 · 2013-02-22T20:36:40.000Z

You don't need to be a fork to pull from the css-social-buttons repo. The whole 'fork' thing only takes effect on GitHub. Just add samcolin's repo to your remotes.

Answer 3 · 2013-02-23T16:36:11.000Z

Yeah... now that I have some commit history and some stars here, I know this :(

Answer 4 · 2013-02-23T22:08:40.000Z

Well… perhaps you could contact GitHub support and ask them to change this repo's status?

Answer 5 · 2013-02-23T22:54:16.000Z

I don't really understand what you're discussing. Is there anything I can do to help?

Sam

Sent from my iPhone
+447840257725

On 23 Feb 2013, at 22:08, Shea Bunge notifications@github.com wrote:

Well… perhaps you could contact GitHub support and ask them to change this repo's status?

—
Reply to this email directly or view it on GitHub.

Answer 6 · 2013-02-23T23:26:24.000Z

Hahah, he was just mentioning you sam, there aren't any problems :)

Answer 7 · 2013-02-24T02:51:27.000Z

Anyway, just something to keep in mind. Being able to fork both repos would be really great, so if you ever find a way that is suitable to you, I'd appreciate it. Good work on the Less version, though ;)