Skip to content

Add spec for incorrect path parsing when name ends with ref

Samantha Ming requested to merge 330947-incorrect-ref-commit-spec into master

What does this MR do?

In a previous MR > !62101 (merged); we fixed a bug regarding a problem when the branch name is the same as the project name when switching ref.

This MR adds feature spec coverage to capture that bug issue.

Scenario Coverage

(This section is copied over from > !62101 (merged))

Create a project name project and a branch called project

  1. Navigate to Repository > Files
  2. Ensure you're on the project branch
  3. Switch to the master branch
  • It successfully switches the branch and no flash message is thrown.
Problem Fixed
problem-when-project-last-name-contains-ref fixed
image image

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

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

Related to #330947 (closed)

Edited by Samantha Ming

Merge request reports

Loading