Adjust relation between desings and versions to be many to many
What does this MR do?
In https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9801 we added the database model to add designs.
But while implementing the entire feature in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10462, it came to the point where we're committing multiple files at once. Which means that a single SHA could point to multiple designs. This means that the relationship between a version and a design needs to change, which is what I've done here
What are the relevant issue numbers?
Part of https://gitlab.com/gitlab-org/gitlab-ee/issues/9492
Does this MR meet the acceptance criteria?
- [-] Changelog entry added, if necessary
- [-] Documentation created/updated via this MR
- [-] Documentation reviewed by technical writer or follow-up review issue created
-
Tests added for this feature/bug - [-] Tested in all supported browsers
-
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides - [-] Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
-
EE specific content should be in the top level /ee
folder - [-] For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
-
Security reports checked/validated by reviewer
Edited by Bob Van Landuyt