pagure

#1076 RFE: Consider creating forks with a remote reference to the main repo
Closed: Invalid Opened by bruno.

Closed: Invalid
Reopen Issue

While people can create these themselves, it might be nice to have one with a standard (within Pagure) name. The reference can be used to move the fork forward without having to delete and recreate it if it is just behind the main repo. You can also do a rebase in some cases as well. (I did git rebase base/master today when I forgot to do a git reset to move forward to the base repo's latest commit before adding some new commits in my fork.)
This doesn't solve all of the problems that can result in having to do normal instead of fast forward, merges between a fork and the main repo, but it does add a small amount of convenience for fixing some cases.

+1

I always add the upstream as an "upstream" remote. The default remote is still "origin".

It seems to me git doesn't support propagating the remotes when cloning:

pagure]$ git remote
github
lcl
origin
pagure
pagure]$ cd ..
$ git clone pagure pagure2
...
$ cd pagure2
pagure2]$ git remote
origin

You are correct. That makes it pointless to set this up on the forked branch.
--mirror will copy over remotes, but it makes a bare clone, which isn't what people normally want.
So I guess this can be closed as invalid.

To do something like this automatically, one can add a post-checkout hook to the templates/hooks directory that makes sure a remote is created if needed. But that needs to be done outside of Pagure.

Let's close then, thanks for your input :)
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.