Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove fork? #540

Closed
chillu opened this issue Jul 30, 2019 · 3 comments
Closed

Remove fork? #540

chillu opened this issue Jul 30, 2019 · 3 comments

Comments

@chillu
Copy link
Contributor

chillu commented Jul 30, 2019

I'm doing contribution analytics over multiple years via gharchive.org. It takes into account repo renames by using the repo id instead. But in this case, we've forked https://github.com/tractorcow/silverstripe-fluent into https://github.com/tractorcow-farm/silverstripe-fluent. What was the purpose of that? Github has a "transfer ownership" function. The effect is that I can't track contributions to the original repo without workarounds, which is a pain when you're doing aggregate analytics over 100s to 1000s of repos. Admittedly, there will be other repos in there with the same issue, but this is one we're particularly interested in getting accurate data for (since it's a supported module)

Can anyone think of a way to resolve this without losing past contribution activity on either repo?

chillu added a commit to silverstripe/supported-modules that referenced this issue Jul 30, 2019
@robbieaverill
Copy link
Contributor

AFAIK it was a transfer rather than a fork, but afterwards if Damian wants to contribute he would do so under his account fork, which would have the same URL as the original 😅

@chillu
Copy link
Contributor Author

chillu commented Jul 31, 2019

Oooooh right, it's that way around

image

That explains why all the issues are on tractorcow-farm. Meaning the fork was created after the transfer, which means I can ignore the new https://github.com/tractorcow/silverstripe-fluent fork, All good, thanks for clarifying

@chillu chillu closed this as completed Jul 31, 2019
@tractorcow
Copy link
Collaborator

Yeah sorry, it was so I could PR back safely. :) Otherwise I'm pushing all my PR branches upstream which is naughty. Even though I did it a few times accidentally haha.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants