Import to GitLab: rebuild Activity and Contribution Analytics page after each import

My activity graph seems to be empty except what I pushed to GitLab's git. Activity graph should be rebuilt after each import.

I'm not 100% in agreement, but also don't 100% disagree.

On one hand I feel like this should only provide contributions from the beginning of your GitLab accounts life, but also I understand that if there are contributions imported from "way back when", they should probably be counted.

Added import label

My activity is mainly in organization so issues that I care about were imported. Importing the activity is important to me as a company owner as I can check the activity of others.

I see you edited your comment so my answer doesn't quite match the current state. Anyways, the second part is still valid, I treat the activity graph as something practical, not just fun. But if that's considered fun, you want developers migrate their GitHub accounts to GitLab and bring their badges with them. ;)

The same problem applies to "Contribution Analytics". GitLab imported all the repos, issues, wikis, and so on from GitHub, yet this is empty. https://gitlab.com/groups/GROUPNAME/analytics

Changed title: Import to GitLab: rebuild Activity page after each import → Import to GitLab: rebuild Activity and Contribution Analytics page after each import

Maybe it makes more sense to let group owners or masters trigger a manual rebuild of all these metrics on all members within a group.

Yeah.. I was thinking about moving all my github projects to gitlab, but that way my activity would be lost. So, until then, I'll keep my projects on github and the new ones i'll start on gitlab.

@lbennett Exactly what @sandrina-p said. GitLab shouldn't underestimate the value of badges. To me as a company owner who hires people, GitHub contributions is a very important factor in hiring. If developers cannot take their badges with them to GitLab, they simply won't move their public activity here.

Our strategy is to make GitLab.com the most popular SaaS solution for private and public repositories. https://about.gitlab.com/gitlab-com/

@Nowaker yhp, exactly that. Also, I subscribe what it was said here about private contributions to show on our activity panel. Do both of that and I'll move to gitlab.

@Nowaker @sandrina-p You've swayed me! If we're importing repos, we're importing commits, issues, merge requests, so on... The contributions graph should be an accurate representation of your whole account.

I'd still love to hear more opinions though!

Maybe @victorwu can weigh in?

added feature proposal label

@lbennett Let me show you an example:

I have this repo on github with commits from August'16 until January'17. Then I imported it to a new gitlab project using gitlab import feature.

As you can see, the commits are recognized to my gitlab account (right email and avatar), but when you check my activity, it is empty.

Thanks @sandrina-p!

/cc @zj

@awhildy : The activity graph design looks like it's borrowed from GitHub. Do we have any plans currently to iterate on it and/or change it?

@regisF / @JobV: What's our plan on supporting scenarios like this, when we import data/projects from other tools, whether one-time or ongoing?

@victorwu

On one hand, it'd be nice to represent only the activity you've done on GitLab so far.

However, on the other hand, there is a strong consideration to help migrating people off other popular tools. If we want GitLab in the future to host major open source projects or even let the activity becomes a kind of an online CV for devs, we need to import the activity so devs don't lose their precious activity in the process.

@victorwu I think the engineering effort to update this after each import is not really worth it.

I also think it's reasonable to say that it's only representing GitLab activity, although I wouldn't be opposed to the opposite either.

Going forward, I think future activity reports etc. should represent all activity in repositories, not just that in GitLab. But then I'm talking about more in-dept, premium features, not this little graph.

not this little graph.

@JobV You really, really shouldn't underestimate the value of this little graph.

@victorwu - There have been some discussions to add some to this graph (such as https://gitlab.com/gitlab-org/gitlab-ce/issues/22645), but no overarching plans to iterate on it. While what we have is borrowed from GitHub, it is a visual people seem to be attached to, and seems to work.

However, let me know if there are specific problems or goals that need to be addressed with it.

This option to rebuild the activity would be great. We just migrated tons of repositories to gitlab.

Hi, like many in here requested, this would be a really nice feature :) Nice as in, really needed!

We are also in the process of restructuring our entire VCS and Deployment setup, and currently importing Bitbucket + Github projects over to Gitlab, and also noted the missing activity logs. A manual rebuild feature would be excellent.

Like Peter Rauber said: This option to rebuild the activity would be great! We also just migrated tons of repositories to gitlab. We are currently using gitlab-ee 9.3.9

Few days ago, i moved my repo from github to gitlab. Gitlab had some awesome features, i really like it. But sadly, i lost all my contributions on github, really upset. It's really nice to have this feature to rebuild the activity!

ZD: https://gitlab.zendesk.com/agent/tickets/83203

I just imported a few projects from my org's self-hosted GitLab CE and my user account got contribution graph updates from old commits. My coworkers, who have contributed to the same repositories and have setup their accounts, see no contribution activity!

Gitlab folks, you may be able to see details here:

https://gitlab.com/vaeit/nextgen

And, one specific coworker,

https://gitlab.com/thomas.barbour

moved to gitlab#6010

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.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

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

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