Add project repository records when creating a project with a repo [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
Normally track_project_repository is called by Projects::CreateService and friends. ProjectRepository is supposed to be the canonical source for the gitaly storage that a project is stored on. Without it some queries will not function. So to make our tests more realistic we should be generating this association when we're dealing with repositories.
We already do this for Snippets. https://gitlab.com/gitlab-org/gitlab/-/blob/05965162fb3c7866fc38c8c078cf02feb83ecd0f/spec/factories/snippets.rb#L31
Noticed while working on !61544 (merged) that the quarantined specs would never work because the query expects project_repository to exist. There are more problems with these specs that I will fix in another MR.
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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