Recreating project history based on git, and commits.

Description

Hello World!

I have little problem with my GitLab. I managed to migrate from problematic source installation (I migrated from 6.X to 9.4). It was painful process. There was many obstacles, but it's natural when you have really old, forgotten but heavily used software. Somewhere in process git hooks stopped working (I don't root cause), unfortunately developers keep working. Some time later someone reported that GitLab is not showing commits on activity stream. I was confused, none of goggled solution worked, so I decided to keep it that way (yeah, not the smartest move ever 😄 ).

Finally I managed to pull our source installation to 9.4.5. Then install omnibus GitLab on separate server (it's so convenient that it should be illegal 💃). Then backup (old source installation) and restore (new shiny omnibus). As said project history is not showing the commits that happen during migration (about 2 weeks).

Proposal

I would like to recreate project history based on commits history. There could be rake task, or whatever, that could achieve this goal.

Links / references

Documentation blurb

Overview

Functionality that allows to create project history based on git commits. Whenever you have problem with git hooks or other GitLab problem, but people still used your GitLab. It should make GitLab migrations foolproof.

It could be used with command line or via UX button.

Fun fact: When you are pushing branches with changes, GitLab is able to recover from 0 commits to proper value on branch. But it requires new commit.

Use cases

Migrating from not fully working GitLab.

I attach also screenshots, that show problem.