Can I manage topics from more than one remote ?

[dod38fr]

Hi

As Debian developer and upstream maintainer, I manage some projects with 2 main remotes:

• Debian package files on salsa.debian.org
• upstream files on gitlab.gnome.org

MR for Debian files are managed on salsa.debian.org and MR and issues for upstream work are managed on gitlab.gnome.org.

Taking Pan project as an example, I have 2 cloned repositories: one for Debian work and one for upstream work. The cloned repo for upstream works enables me to manage issues and PR using forge 👍 .

I'd like to use git worktrees to manage both sides of this project.

Starting from Pan cloned repo used for upstream work, I've created a new worktree for Debian work.

Unfortunately, Debian worktree shows the topics from gnome remote. I cannot see any way to manage Debian topics in this worktree.

Is there a way to manage topics coming from more than one remote ?

All the best

[tarsius]

You can set the Git variable forge.remote to different values in different worktrees.

[dod38fr]

Should I set forge.remote to the remote name or the URL ?

Using git config set, this value is written in the .git.config of the main dir (not in the worktree dir). How can Forge know which worktree this applies to ?

[tarsius]

Should I set forge.remote to the remote name or the URL ?

The name.

Using git config set, this value is written in the .git.config of the main dir (not in the worktree dir). How can Forge know which worktree this applies to ?

Turns out, Git does not by default use a per-worktree config file. You'll need git config extensions.worktreeConfig true. See git-worktree(1) for more information.

But unfortunately there's also an issue on Forge's side. So I'm changing this to a feature request, and will look into it when I don't have many other things on my plate, which could take a few weeks.

[dod38fr]

No problem. I'll keep my 2 separate directories until this is fixed.