Add option to mirror an upstream repository.
Closes internal https://dev.gitlab.org/gitlab/gitlab-ee/issues/279
Depends on gitlab-shell!29 (merged)
To do:
-
Decide on what user should be the author of the activity feed events. The initial project creator perhaps? That makes sense for personal projects, but less so for group projects, where it's even possible that the creator has since left the team. -
Write specs! -
Write documentation -
Port back relevant commits to CE: gitlab-org/gitlab-ce!1822
Mirror status on project homepage
Settings navigation item
Mirroring settings
Activity feed with new "pushes" (mirror updates)
I have yet to decide on what user should be the author of these events. The initial project creator perhaps? That makes sense for personal projects, but less so for group projects, where it's even possible that the creator has since left the team.
Warning that branch has diverged from upstream
Commits heading after failed update
Link send user to the mirroring settings if they are a project admin.
Mirroring settings after failed update
New project page
Import form after failed import
(Screenshot outdated)
Shown when the initial import of a project fails, not when an update of an existing project fails.
Merge request reports
Activity
Looks awesome @DouweM
(except the messy thing in the project dashboard ;) )
Edited by Job van der Voort- How it handles StrictHostKeyChecking for SSH?
- Can I use my private SSH key? Adding GitLab Public Key is security issue when you are working on shared GitLab instance.
Very nice @DouweM! The green 'last updated' banner seems like some user action happened. Do you think we can make this appear inline somewhere else instead of the green banner?
I'm not sure about the user to tie to updates, either. More and more I think we need some system notes/updates like this to be 'author-less' - something to think about.
@DouweM I love it!
The green 'last updated' banner seems like some user action happened. Do you think we can make this appear inline somewhere else instead of the green banner?
Agreed. What about moving this text under the "Update Now" button, right-aligned, on that settings page?
Edited by Robert SpeicherUpdate now button to the row with other buttons.
Gray box inside red looks extremely ugly
Suggestions? :)
@ayufan As discussed in the internal thread, no work at all has been done on importing from SSH, besides allowing SSH URLs. Everything else is (currently) the user's responsibility to set up. Do you have any concrete suggestions on how to improve this?
I'm not sure about the user to tie to updates, either. More and more I think we need some system notes/updates like this to be 'author-less' - something to think about.
I will investigate how much work it is to have "system events"
The green 'last updated' banner seems like some user action happened. Do you think we can make this appear inline somewhere else instead of the green banner?
Agreed. What about moving this text under the "Update Now" button, right-aligned, on that settings page?
Good idea, will try that out.
Added 1 commit:
- 3c227a7c - Fix update mirror tooltip.
Added 225 commits:
-
add24b04...e64f2da6 - 222 commits from branch
master - 76d96363 - Merge branch 'master' into mirror-repository
- 3400b3c8 - Better error handling.
- ce27d574 - Allow mirror user to be set.
Toggle commit list-
add24b04...e64f2da6 - 222 commits from branch
@rspeicher Please review implementation and documentation.
Added 1 commit:
- f8451830 - Add documentation.
Reassigned to @rspeicher
mentioned in merge request gitlab-shell!29 (merged)
