pagure

#4216 Edit in your fork doesn't work when my fork is old
Opened by churchyard. Modified

Open
Close Issue

https://pagure.io/fedora-comps/blob/master/f/comps-f30.xml.in

I have forked this repo long time ago:

in fact my fork's master is so old that it doesn't have this file:

https://pagure.io/fork/churchyard/fedora-comps/tree/master

When i click Edit in your fork, I get 404:

png

I understand what happens here, but it is not really user friendly. I want to edit current upstream master and commit it to a new branch in my fork. I don't really care what state my fork's master is.

But what if your fork was ahead of the main repo, how should pagure behave then? Go back to the current master? How would it look if you then commit your change?

I agree with the not very user-friendly, how to get it right is the tricky part :)

it should always create a new branch derived form the branch you are trying to edit.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.