Thanks Junio. Yep, I see where I went wrong now and learned something new in the process. I ended up using the following configuration in order to explicitly fetch/push branches, notes, and tags: [remote "origin"] url = https://github.com/bkuhlmann/test fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/notes/*:refs/notes/* fetch = +refs/tags/*:refs/tags/* push = +refs/heads/*:refs/remotes/origin/* push = +refs/notes/*:refs/notes/* push = +refs/tags/*:refs/tags/* The only problem is my feature branch never shows up on the remote. If I amend my commits, rebase them, and/or update the commit notes, the changes, once pushed, don't show up on the remote repository. I do see this in the output: To https://github.com/bkuhlmann/test 709004099276..1eefe6a1101c refs/notes/commits -> refs/notes/commits + a966604d7864...e0a75df6084f release -> origin/release (forced update) Seeing "forced update" in the output is strange because I'm using `git push` and not `git push --force-with-lease`. Am I still missing a configuration setting that I should be aware of? I'm not getting errors but the output is odd. > On Aug 6, 2023, at 7:07 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Brooke Kuhlmann <brooke@xxxxxxxxxxxxx> writes: > >> ... o why default branch push behavior is being >> ignored/overwritten. > > The root of your confusion lies around here, I think. The "default" > branch push behaviour is given only when you do not customize. Once > you add customization, you would specify _exactly_ what you want. > > In other words, the customization is NOT something you tell Git to > do _in addition to_ what it does anyway (otherwise you would not be > able to configure _away_ what is usually done by default when you do > not want to see it done). >
