Add a table for design repo and a class for the corresponding git repo
What does this MR do and why?
Describe in detail what your merge request does and why.
Geo needs a model representing design repos to be able to replicate and verify them using the Self-service Framework in #355660 (closed)
To that end, this MR re-factors the class DesignManagement::Repository
such that it now represents a project's design repo on the whole, while a new class, DesignManagement::GitRepository
is a wrapper for the corresponding GitLab managed git repo.
The calls to the git repo stay the same, because the Repository class simply
delegates the method calls to DesignManagement::Repository.git_repo
.
DesignManagement::Repository
, is now backed by a table, associating the design repo to the project is belongs to. This table will be backfilled in another iteration, tracked here #391191 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.