Thanks. We do name our branches that way, and always know what’s in them. The question is more about monitoring state change between the time the PR gets approved and when it finally gets merged into Master. Any given branch has to go through internal QA, then customer QA, then be combined into a release, etc.
Everyone knows this popular graphic:
Every color (dots) is a branch. How do you keep track of them all!? For us, I want to be able to test all those purple dots before I merge them into the develop.
We use 3rd party tools for ticketing and workflow…it seems like it would be nice to be able to look at a branch (list) and know “this one has been tested” and “this one is just sitting here abandoned”. The commit graph gives a nice indicator of ahead/behind master, but that’s all we’ve got.