git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Help: Trying to setup triangular workflow

From
MGMatthew B. Gray <hey@matthew.nz>
Date
Jan 13, 2024, 00:45 UTC
Message-ID
<bf59af5d-1a59-41bb-b693-087b940e266b@app.fastmail.com>
In-Reply-To
<20240112073136.GG618729@coredump.intra.peff.net>
Hi Peff,
> This push step is rewriting your upstream config. Do you have
> push.autoSetupRemote configured? In general you wouldn't want that for a
> triangular flow.
 
Thanks for the pointer, yes have both push.autoSetupRemote and
branch.autoSetupMerge set. Turning these off has fixed my problem.
With neither option set the example yields:
  @{upstream}: refs/remotes/origin/main
  @{push}: refs/remotes/myfork/mybranch
With push.autosetupremote=true set:
  @{upstream}: refs/remotes/origin/main
  @{push}: refs/remotes/myfork/mybranch
With branch.autoSetupMerge=simple set:
  @{upstream}:
  @{push}: refs/remotes/myfork/mybranch
With branch.autoSetupMerge=simple and push.autosetupremote=true:
  @{upstream}: refs/remotes/myfork/mybranch
  @{push}: refs/remotes/myfork/mybranch
> Though I think it also is only supposed to kick in if there is no
> tracking configured already. Why did the "git switch" invocation not set
> up tracking itself? When I run those commands it does. Do you have
> branch.autoSetupMerge turned off in your config?

If you're interested in looking at my full gitconfig it's hosted here: https://github.com/heymatthew/dotfiles/blob/trunk/softlinks/.gitconfig

However looks like taking those out of global config has fixed my issue. Thanks for the help!

Ngā mihi, Matthew

Previous: Jeff King
Message 3 of 3 in “Help: Trying to setup triangular workflow”
  1. Matthew B. GrayJan 12, 2024
  2. Jeff KingJan 12, 2024
  3. Matthew B. GrayJan 13, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.