You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the github api or some similar api identifies repo B as being forked from repo A and branch B:C is either equal to or "behind" the commits of A:C (i.e. commits ahead/behind master), I would suggest suppressing the listing of repo B from the landing page.
i.e. there's little utility in my fork of psalm showing up on the landing page when the master branch is always either equal to or behind the master branch of vimeo/psalm
The text was updated successfully, but these errors were encountered:
If the github api or some similar api identifies repo B as being forked from repo A and branch B:C is either equal to or "behind" the commits of A:C (i.e. commits ahead/behind master), I would suggest suppressing the listing of repo B from the landing page.
i.e. there's little utility in my fork of psalm showing up on the landing page when the master branch is always either equal to or behind the master branch of vimeo/psalm
The text was updated successfully, but these errors were encountered: