Choose head remote about hupkit HOT 6 CLOSED

Btw, I'll be glad to help you out to make this work if it comply to what you think we have to do for this tool 😄

from hupkit.

What is the use-case for this?

Upstream points to the "root" of the repository (not your own fork) and is used for determining the organization and repository. In fact, origin is only used for updating and cleaning-up of your own pull requests.

from hupkit.

I'm maintaining some repositories where I use the repository as origin (I don't have fork for it, probably bad design here).

But I'm also using it for repositories with a fork (and the upstream / origin usual case)

from hupkit.

Since #108 it's possible to store addition configuration for the repository (with the repository itself), this might solve this use-case?

# config.php in "_hubkit" branch (actual configuration is Php, yaml only used as example)
schema_version: 2

host: github.com
repository: 'rollerworks/search'

from hupkit.

This issue was related to choose the branch, not the repository. It would require a new configuration field.

from hupkit.

You mean using a different branch than main/master? I believe we can use a configuration for this, as the configuration file is stored in a separate location (the _hubkit branch).

In fact, looking at the current implementation, for upmerge the GitHub default-branch is used, but else where the primary-branch (Git config init.defaultbranch) is used 🤔

I think it's best to use the GitHub default-branch everywhere to minimize configuration maintenance.

Otherwise can you give some more details about your set-up?

Sorry for the late reply.

from hupkit.