You may need to think how this fits into releases. some things to consider: - Do you want the release to contain test information or not? A lot of Apache project do include that but some don’t - it may be size dependant. - Do you wan users to be able to easy test releases? (Not providing test infrastructure in the same releases may make that harder). - This is a common scenario, a user is on an old version and needs to test it, the new testing repo has been updated to work with teh latest release, how do they test it?
I don't know if such a repository would contain user usable testing of not. Its primary purpose would be to integrate testing on github and support the change workflow.
This is nothing set in concrete and just a thought experiment. There is no workflow or testing plan in place.
