-
Notifications
You must be signed in to change notification settings - Fork 24
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
forked projects with different name not related with base repository are not being considered #157
Comments
wondering whether we should consider to treat this case... 🤔 |
wasn't this already fixed in #156 ? |
Dunno :). Sadly GitHub didn't leave enough breadcrumbs for me to be able to recall what I suggested... -- it's likely my suggestion was to check to see if two commits were reachable for the same sha across the fork world (with the same content...), as generally github has treated connected repositories as a single repository. (Amusingly, github's current search engine currently treats identical individual documents from unrelated repositories as equivalent -- this is discernible today because the counts don't treat them as distinct when a search hits each of them...) I will say that it's possible for a user to have:
|
so @jsoref to summarize you still have this issue with a repository not being considered, right? |
I don't think I use this action. I'm here because I use lots of repositories and was involved in GitHub's prototype community. I offered input based on a question and someone filed this issue and tagged me. It should be easy enough to test to confirm... |
ok, thanks for clarifying |
We are considering forked projects:
Still pending:
-the ones with the different name as the base repository and not related with it
@jsoref https://github.com/jsoref/ suggested a very interesting approach we should at least consider https://github.community/t/github-api-getting-fork-project-for-a-specific-user/185441/3?u=ginxo
The text was updated successfully, but these errors were encountered: