Step 5: Version Control for Snippets: Development of the Migration Plan (MVP)
Important: All the new functionality must be implemented behind the feature flag :version_snippets
. Besides, it has to be scoped for projects. Therefore, instead of checking if the feature flag is enabled or not (Feature.enabled?(:version_snippets)
), we will check if the feature flag is enabled for specific projects (Feature.enabled?(:version_snippets, project)
). This way, for testing purposes, we can enable the feature flag on the project gitlab-org/gitlab
for example, instead of enabling it globally.
This issue represents the development of the Migration Plan. The output of this issue will be the migration file.
Migration aside, when we reach this point the feature flag should have been removed. This would mean that any new snippet will create automatically the snippet repository if flag enabled. Every snippet update will involve a repository update and every deletion will remove the repository as well. The import/export process, should automatically create a repository and commit the information inside the content
column in the repository.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.