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

repo mess #439

Closed
grinapo opened this issue Jan 16, 2017 · 4 comments
Closed

repo mess #439

grinapo opened this issue Jan 16, 2017 · 4 comments
Labels
P3 Low priority
Milestone

Comments

@grinapo
Copy link

grinapo commented Jan 16, 2017

Since there is no network display for Tox* repos on github due to the large amount of forks there seems to be no way to see which repo merges which one and which one should be, well, used and why.

Would it be possible to update the top of the readme to clarify where this repo stands within the 1039 (and counting) forks and the bunch which are updated periodically? Do you merge any of them here or does yours get merged into the "main" (irungentoo?)?

(If they don't get merged - is there any reason you don't merge all the changes around, "forcing" others to use your repo as the most complete? :-))

@GrayHatter
Copy link

This repo is the most up to date, and no one is forced to use this repo, any more than someone is force to drive a Honda instead of a Toyota. Any repo can pull the commit from this one into their own. For all the other repos, only the owner can merge it. TokTok can't force other developers to accept new code.

@iphydf
Copy link
Member

iphydf commented Jan 16, 2017

@grinapo can you file an issue on https://github.com/TokTok/github-tools/issues about generating a repo graph that considers "recently updated"? We can probably just generate that graph once a day. It would also be useful for discovering new, active forks.

@iphydf
Copy link
Member

iphydf commented Jan 16, 2017

Please file an issue on github-tools.

@grinapo
Copy link
Author

grinapo commented Jan 20, 2017

@GrayHatter just to clarify:

  • by "forcing" I mean my experience that if there are 50+ repos, and I merge all of their changes into one repo of mine, and I actively keep pulling in others' changes then people start using my repo and they start to create PRs for my repo, since people want to use one with all the fixes instead of picking one with 1/10th of the fixes. :-)
  • by pulling I meant to merge foreign changes into this repo (I understand you've already done that)

@robinlinden robinlinden modified the milestone: v0.2.11 Mar 20, 2020
@iphydf iphydf added this to the meta milestone Feb 4, 2022
@iphydf iphydf added the P3 Low priority label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low priority
Projects
None yet
Development

No branches or pull requests

4 participants