Learn more about these different git repos.
Other Git URLs
When moves with no content change occur in the commit, Pagure doesn't recognize it as a move, and renders a full delete+create diff of the file, as seen below:
<img alt="Screenshot_20180610_215551.png" src="/pagure/issue/raw/f9b58530b45f6f88df6b75cf5543f4a005c0f7e18a7eada60446e381cc6d6c13-Screenshot_20180610_215551.png" /> <img alt="Screenshot_20180610_215602.png" src="/pagure/issue/raw/files/34e81623f1e5e8af01efca6f2719923e6680f40e9efd3ba611d3736b07e258fb-Screenshot_20180610_215602.png" />
In contrast, GitLab and GitHub both recognize this kind of operation and render no diff content in this case, making changes a lot less burdensome to analyze.
Since it failed to upload initially... <img alt="Screenshot_20180610_215602.png" src="/pagure/issue/raw/files/34e81623f1e5e8af01efca6f2719923e6680f40e9efd3ba611d3736b07e258fb-Screenshot_20180610_215602.png" />
I'm pretty sure we used to support that.
Mind testing on stg.pagure.io ?
@pingou, it's broken there too: https://stg.pagure.io/rpm-packages/pagure/c/93362d23e1297b5e94532e8bfed05e8e7250ff98
Metadata Update from @pingou: - Issue tagged with: bug
pretty sure that the logic is there on the pull-request page, it just looks like it is not there in the commit view.
THis is now fixed in the commit view with the recent changes there in the new UI.
Metadata Update from @ryanlerch: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.