It’s a bit tricky with so many builds floating around, I know.
Internally at Epic our artists work in the master branch, and QA do a quick test pass to make sure that a build is stable before pushing it out to the team. We find that’s a good balance between latency and stability, though we’re often firefighting issues that spring up. I periodically tag and upload dependency zips for one of these promoted builds on GitHub.
Personally, I’d stick with one of the release branches unless you’re reliant on some bleeding-edge feature. There are often several hundred fixes that go into those builds while any features are frozen.