Compare View across forks

It is handy to compare differences across repos, when one repo is a fork of another. Here is an example of such a Compare view on github - https://github.com/ellekasai/resumecards/compare/gh-pages...weitzman:master

mentioned in issue #20008 (closed)

@haynes this sounds like a ~"feature proposal". Would you mind adding the label? Alternatively, should this be closed with preference for #20008 (closed)?

@jamietanna Thank you :)

I think they are related, but slightly different.

added ~14213 label

Hi,

First of all, thank you for raising an issue to help improve the GitLab product. This issue was labelled as a ~"feature proposal" in the past. In order to maintain order in the issue tracker, we are starting to close off old, unpopular feature proposals that have not gained many votes since opening.

This issue will be marked for closure, as it meets the following criteria:

• Created over 1 year ago
• Labelled as a ~"feature proposal"
• Unscheduled (not associated with a milestone)
• Less than 10 upvotes

Thanks for your help and please raise any new feature proposals as a new issue.

/cc @markglenfletcher

added auto updated awaiting feedback labels

We are reverting the above policy regarding old, feature proposals until we find a better solution. Sorry for the noise.

The issue will no longer be marked for closure.

removed auto updated awaiting feedback labels

added auto updated potential proposal labels

/cc @jramsay

added ~2278658 forking repository labels

added devopscreate label

added to epic &264

added Create [DEPRECATED] and removed ~2278658 labels

mentioned in epic &264

added [deprecated] Accepting merge requests label

mentioned in epic &687 (closed)

added groupsource code label and removed auto updated potential proposal labels

mentioned in epic &264

changed epic to &1421 (closed)

Any update on this ? btw, 15 upvotes as of today for this issue (>10 upvotes)

My team just switched to gitlab from bitbucket. My colleagues and I are glad we made the move since gitlab is so fun to work with and intuitive. Not losing the possibility to compare branches across forks would be the icing on the cake really. Keep it up ;-)

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks.

As part of this migration, issues will be moved to the current gitlab-ee project. We are starting with moving issues that have been created at least a year ago, and are not part of the current milestone.

If you have any questions about all of this, please ask them in our dedicated FAQ issue. You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

removed time estimate

changed milestone to %Next 4-6 releases

added sectiondev label