So, I'm looking at https://github.com/openwrt/packages/ and see the new openwrt-24.10 branch, and being That Guy, I want to stay ahead of the curve. I go to my fork https://github.com/efahl/packages/ and click our friend the Sync fork button, expecting it create the new branch in my fork. No go. (Has github changed this behavior? Seems to me it worked on the 23.05 branch? Someone with a working time machine, please go back about 18 months and check in with me as I can't remember what I did then.)
I found this:
Does that look the best way to do it, or am I missing yet another arcane git incantation in my book of spells?
Note: this should work exactly the same for packages, I just don't have that pulled down atm so just used openwrt.git instead.
I haven't used the GitHub UI but the following has worked for me in the CLI (make sure all remotes are fetched before this, I assume origin is your fork and upstream is openwrt/openwrt.git):
At this point the branch should exist in your fork and GitHub should detect it as a fork as the branch has the same name as upstream. I even tried to hard reset with git reset --hard HEAD~1 and I was then prompted to sync in the GitHub UI.