Handle empty project within Security Configuration
What does this MR do?
Addresses the error found in Sentry that occurs on the Security Configuration page when a project does not yet have a repository.
The call to the project history path was blowing up, and since we can't link to it, we return an empty string and the link does not get displayed.
This prevents the entire Security Configuration page from blowing up.
Screenshots (strongly suggested)
Here is the View History link that shows under normal circumstances:
And here, that link is gone because there is no .gitlab-ci.yml to have any history. We will now not not be showing the link if there is no repository associated with a project or if there is no default branch set:
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
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
Related to #262626 (closed)