Learn more about these different git repos.
Other Git URLs
If I have an older fork of a project, my master branch is probably not up-to-date anymore. Now, when I go to a file on the master branch and click "Fork & edit", I get forwarded to the edit page within my forked version of the project.
The problem is that the file that it shows me to edit is the old version of the file, because Pagure didn't update my fork.
Pagure should either update my fork, or create a new branch on my fork with a recent clone of the branch on which I hit the "fork and edit" button.
Commenting here rather than filing a new issue, as I think this is likely to be related: when using Fork and Edit with an old clone, and selecting to create a new branch for the change, Pagure doesn't actually create the new branch, it just 404s trying to access it.
Fork and Edit
Metadata Update from @wombelix: - Issue set to the milestone: 5.13
No update since 5 years but still worth looking into if the issue still exist and can somehow addressed for the next 5.13 minor release.
That one is definitely still valid, but I've no clear idea on how to fix it :(
Login to comment on this ticket.