What I'm saying is, I feel like this functionality should be available by default in a new Git-based workflow, as it would be the only way to have access to build results when working outside of OBS. Having to set up Git<->OBS integration manually for every fork of every repo I would ever interact with on src.opensuse.org sounds like a lot of work. I agree with Filippo here, setting up the integration yourself for every fork is pointless busywork and makes the git based workflow *worse* than the existing workflow on OBS.
I'm not suggesting that it needs to be manually set up. Every pool package needs to bring its testing qualities (some might be fine with a build check, some might want to have more etc). and I agree that branching those gits should also bring that to the git branches. My current limited understanding of how the git-scm workflows work is that you already have that functionality. I'll set it up as an example to learn more about that. Greetings, Dirk