Squash project templates on update
What does this MR do?
Follow up on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31174 with fixes for the rake task gitlab:update_project_templates.
Prior to this MR, a template bundle updated via that task would include all branches and commits from the source repository, which is not the desired behaviour. Instead, the template bundle should include just the source code and a single standard commit explaining how the repository came to be. For example, Initialized from 'Ruby on Rails' project template.
This MR fixes that by creating a new repository from a source dump instead of doing a repository import. This approach is a bit faster, but also hackier, as it involves directly pushing to a file:// URL. I do not see this as a showstopper, as the code has only ever been meant to be used from a development environment.
Motivated by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31310
Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/46043 and https://gitlab.com/gitlab-org/gitlab-ce/issues/58204.
Example gif
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios. -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team