nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to properly display renamed or moved files in new pull request experience?

Mateusz Jabłoński

I am using new pull request experience and have noticed an issue, which makes it almost impossible to work.

There is no way to determine, which files were renamed or moved between directories. If I move a file or rename a file, they all are marked as removed from previous path, and created at current path. Is this an BitBucket issue, or is there some option to change the way it is displayed?

Old experience works exactly as expected - files are marked as moved, and I can even see the changes within this moved file, if there are any.

Accepted answers

seanaty

We're still working on the kinks in the new pull request experience. This is a known issue that we are tracking here: https://jira.atlassian.com/browse/BCLOUD-19752

All comments

Lenin Raj

Hi @Mateusz Jabłoński

This is interesting, can you please share the screenshots of the same PR from the old pull request page and the new pull request page?

Mateusz Jabłoński

Sure.

What I did in this PR, is:

renamed file DesignSchemaJson_MOCK.swift to DesignSchemaJSON.swift
created new DesignSchemaJSON_MOCK.swift file with different content

In old experience, I see exactly what I did - rename with no change + new file.

List view:

Code view:

But in new experience, this is what I see - 2 new files, and 1 removal.

List view:

Zrzut ekranu 2020-01-14 o 13.14.07.png

Code view:

I have this issue with every single moved or renamed file in every project hosted on BitBucket.

seanaty

We're still working on the kinks in the new pull request experience. This is a known issue that we are tracking here: https://jira.atlassian.com/browse/BCLOUD-19752

Mateusz Jabłoński

@seanaty The issue you have linked consists of two separate errors. The problem with renaming/moving files exists regardless of the size of file. In general, file can be even empty, and the same problem still occurs. I think it should be a separate issue with medium priority, as stated in the issue comments.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

pull-request