+1
On Wed 10. Jan 2018 at 22:02, Wojciech Trocki <wtrocki@redhat.com> wrote:
Easiest way to remove forks will be to remove all upstream repositories.
I have tested that on sample repository.
After removing upstream all downstream repositories will no longer be there as forked.
Indexing works as well.
We can test that with https://github.com/aerogearcatalog/keycloak-apb_______________________________________________On Wed, Jan 10, 2018 at 8:53 PM, Wei Li <weil@redhat.com> wrote:+1--On Wed, Jan 10, 2018 at 3:21 PM, Aiden Keating <akeating@redhat.com> wrote:I think this is a really good idea.The fork could be quite confusing at first glance for people.It sort of appears that you're not on the "correct" repo, even though you are.On Wed, Jan 10, 2018 at 2:48 PM, Wojciech Trocki <wtrocki@redhat.com> wrote:_______________________________________________Do you guys think it's possible to remove forks from https://github.com/aerogearcatalog repositories?All repositories are now forked from private account. For example:is forked from:https://github.com/aidenkeating/keycloak-apb
As result of that github it's not indexing them properly.It may be also confusing for community to know what upstream they should target with the changes.Regards--
feedhenry-dev mailing list
feedhenry-dev@redhat.com
https://www.redhat.com/mailman/listinfo/feedhenry-dev
_______________________________________________
feedhenry-dev mailing list
feedhenry-dev@redhat.com
https://www.redhat.com/mailman/listinfo/feedhenry-dev
--
feedhenry-dev mailing list
feedhenry-dev@redhat.com
https://www.redhat.com/mailman/listinfo/feedhenry-dev
