Tootfinder

New on blog: "How we incidentally uncovered a 7-year old bug in gentoo-ci"
"""
“Gentoo CI” is the service providing periodic linting for the Gentoo repository. It is a part of the Repository mirror and CI project that I’ve started in 2015. Of course, it all started as a temporary third-party solution, but it persisted, was integrated into Gentoo Infrastructure and grew organically into quite a monstrosity.
It’s imperfect in many ways. In particular, it has only some degree of error recovery and when things go wrong beyond that, it requires a manual fix. Often the “fix” is to stop mirroring a problematic repository. Over time, I’ve started having serious doubts about the project, and proposed sunsetting most of it.
Lately, things have been getting worse. What started as a minor change in behavior of Git triggered a whole cascade of failures, leading to me finally announcing the deadline for sunsetting the mirroring of third-party repositories, and starting ripping non-critical bits out of it. Interesting enough, this whole process led me to finally discover the root cause of most of these failures — a bug that has existed since the very early version of the code, but happened to be hidden by the hacky error recovery code. Here’s the story of it.
"""
#Gentoo

I feel stupid for asking this… but is there still no good way to checkout and later pull a pull request branch from another repo?
We've got `gh pr checkout NUMBER` but the only way I've found to fetch updates is to delete the local branch and start over.
I really don't want to play adlib with manually adding remotes etc – is this still the best we can do in 2025??
EDIT: it’s solved! 🎉

Tomáš Janoušek (@liskin@genserver.social)
@hynek @carlton Drop fetch.all=true and that fixes it.You may need to learn to use git remote update instead of git fetch though.And I’d consider filing this as a bug upstream, because as you said ...