Corrective actions for rendering file content for branches that have slash and hash
From a recent customer incident, the deployment broke the rendering for branches that has / in them.
This is directly involved with our customer's day to day workflow.
We need to do an audit in our test coverage to make sure that this is covered in all cases and that the development teams have this in mind when developing and making changes that affect code and files.
Possibly related gitlab-org/gitlab!29027 (merged)
- Support request https://support.gitlab.com/hc/en-us/requests/154128
- RCA: gitlab-org/gitlab#215099 (closed)
Context from customer
- The UI fails to render correctly for any branch that has a / in the name.
- File tree does not display on branches with a / in the name.
Plan
Ensure that we cover the use case for branch names in all places that brachnames are shown or is a dependency of.
- File views from branches
- Merge request diffs
- Branch view and navigation
CC @edjdev
Edited by Mek Stittri