I'd like to see all forked projects of one project

You have on the project home page a button which show us a quantity of forks from one project.

I'd like to see all forked projects of one project (even mine).

How could we see all forked projects of any project?

Also requested on https://news.ycombinator.com/item?id=10236958

Added ~12742 ~19492 labels

Reassigned to @creamzy

Milestone changed to 8.2

@adrianovieira I think you asking for page with list of forks right? Similar to what GitHub has on members page?

@creamzy I think this issue is about separate page where you can see list of forks (see screenshot above). It has nothing to do with GitLab Network page. You might be confused by link to HN.

According to HN link. From user comment I see its about extending Network page with branches/merged from forks for cases when users use fork workflow. This should be separate issue and discussion before we might consider implementing it. Problem with this approach is that it should not affect performance and should work for big amount of forks. Otherwise we get useless page like this:

@dzaporozhets I learned about extra difficulties of fork btn implementation and that is why I need to move milestone further. My initial idea was to introduce split btn Fork/ # of forks, where # of forks would lead to forked projects page. But to do it, we need to figure out how to solve split btn issue.

What milestone can you advise? I will attach design tomorrow anyway and unassign the issue but need to add milestone not to lose it. Maybe 8.4?

Milestone changed to 8.3

@creamzy Both 8.3 and 8.4 ok for me. Split button is file also. Thanks

I prefer not to use tree view as it is almost impossible to navigate it in case there are lot's of forks, and one can end up with a lot of good code lost around that never makes its way back upstream. @dzaporozhets @adrianovieira how do you like this approach, when the structure is flat, but self-explanatory and easily sortable?

@creamzy The projects list rendering is different from what we have on other pages. Any reason why we do it like this?

Also what is Following and Yours tabs?

@dzaporozhets Following is Starred , my bet. Yours is your own forks, if it makes sense from dev perspective.

As for the current project list, I know but it has no activity tracing, like last update, or creation date, so you can't really understand the value behind the fork. As fork is not necessary yours.

I do believe we have all this info available and just need to manifest it. If it's not like that I can use current project list view.

PS As for avatars, we gonna change their sizes to cut sizes variations to 2 main,so no worries. And I will switch blue colour to the grey as in the project list.

Updated list view, based on the discussion with @dzaporozhets. We can add Fork Button to the top nav or in the same row with filter and search

Added ~127618 and removed ~19492 labels

Assignee removed

Added frontend and removed ~127618 labels

@creamzy Page looks good. I am not sure about green fork button at top panel. What is the purpose of the button?

@dzaporozhets to fork the project, as suggested, we can put it to the filter/search part

@creamzy we already have fork button on project home page. Do you think its necessary to duplicate it on Forks page?

Most of the views from the left sidebar have their unique action, like Merge Requests - New Merge request, milestones - New Milestone, in general we can support the same approach by promoting Fork Action,

or do you think it is enough to have it on a project home page @dzaporozhets ?

It is not a duplication, more like promoting most possible action in the context of an open screen.

@creamzy makes sense. But on other pages button is not on navbar but on page itself. So I think we should do the same here

@dzaporozhets source file is updated

@creamzy thank you!

mentioned in issue #2876 (closed)

Added ~127618 label

Milestone changed to 8.4

Added ~122770 label

Added ~123454 label

Added feature proposal label

Reassigned to @rdavila

@creamzy can I have access to the sources files for this design?

Let me contact you after the team call and explain how to find it. @rdavila

mentioned in merge request !2376 (merged)

@dzaporozhets @creamzy do you agree if I show the last commit message as the description of the fork?

@dzaporozhets @creamzy just to double check: a protected fork is a one where the current user doesn't have read permissions?

@creamzy I'm thinking in two additional scenarios:

1. When the current user has already forked the project. Should we hide the fork button or show a link to the fork?
2. When there aren't forks, can you provide a single mock for this please?

do you agree if I show the last commit message as the description of the fork?

@rdavila yes since description is repeating

just to double check: a protected fork is a one where the current user doesn't have read permissions?

yes. Maybe give it different wording to prevent confusion

When the current user has already forked the project. Should we hide the fork button or show a link to the fork?

I would say "link to fork"

When there aren't forks, can you provide a single mock for this please?

probably just "no forks text"

just to double check: a protected fork is a one where the current user doesn't have read permissions? yes.

Maybe give it different wording to prevent confusion

I've changed protected by private

This is how it's looking until now:

thanks for the feedback @dzaporozhets.

@rdavila looks good for me!

@rdavila

When the current user has already forked the project. Should we hide the fork button or show a link to the fork?

The Button changes to forked, on the project page, and here Link to fork should work the best, oh I see @dzaporozhets has already mentioned it.

When there aren't forks, can you provide a single mock for this please?

Your mockup looks great. Let's keep it like that for now. Empty states is another issue I need to prepare

Everything looks good so far, thank you so much

@creamzy I need some help with positioning some elements with CSS, please ping me when you're available on Slack.

Here is the last screenshot with the icon and the sort dropdown working:

I'm going to add some specs and send it for review later.

@dzaporozhets how does it align with your current full width layout? does @rdavila need to change something?

@creamzy It should be fine. I kept compatibility for most pages. @rdavila just rebase on latest master and check that it looks good and uses new classes.

. @rdavila just rebase on latest master and check that it looks good and uses new classes.

@dzaporozhets I've rebased with master and it looks good, however I'm not aware of the new classes so I don't really know how to use them.

@creamzy @dzaporozhets here is how it's looking now:

No Forks

With private Forks.

Without private Forks.

@rdavila there are few issues with vertical alignment of Fork button, search field, text etc. Try to fix it otherwise ask @jschatz1 to help you. UI should look perfect like on screenshot from https://gitlab.com/gitlab-org/gitlab-ce/issues/2406#note_3171509

@dzaporozhets thanks for the feedback, @jschatz1 is going to jump into it.

Reassigned to @jschatz1

mentioned in commit 7765ce18

mentioned in commit 2b05bf4b

mentioned in commit b2e5b57f

mentioned in commit 3b75d65b

mentioned in commit 55707f95

mentioned in commit f0b7dcba

mentioned in commit e4d26966

mentioned in commit b6170d2d

mentioned in commit b0a5a99e

mentioned in commit 5cba5924

mentioned in commit 40e1ad90

mentioned in commit 833a0f4d

Status changed to closed by merge request !2376 (merged)

mentioned in commit 88e16c3d