Sorry a bit flippant.
I think my point is that where changes have been made for a user, and they are asked to test them, it would be useful for there to be a branch that enables that. Master is used by a number of people and merging what is in effect un-tested changes could have negative effects. It would, I feel, enable quick fixes to be created where necessary.
Dev - relatively un tested fixes/development - potentially unstable changes but available to all
Master - pre-release - stable changes
Stable - Tagged releases.
Not everything would need to pass through dev, but a ‘fix’ that is not tested shouldn’t be merged to a mainstream branch IMHO.
The key thing for me is to offer a simple route for users to test fixes. The ability to switch branches via the UI would be useful, but it needs to be selective by Repo I suggest .
Also, I’d like to see the merges to master happening more often. I like the Home Assistant weekly cycle but that is a bigger project. Stable is currently 52 commits behind master and the release versions are completely out of kilter. Last ‘release’ was Nov.