Adds a Gitaly n+1 notice to commit handling on access check
What does this MR do?
Adds a Gitaly n+1 notice to commit handling on access check
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
It will prevent developers from hitting random errors because of his, until we can solve the underlying n+1 issue.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together