This thread is trying to answer question "What is the best practices for GitHub repositories with your Playwright assets? Should you share the repository with the source code for the target applications or use separate repositories?"
I have separate repos (but as @skorp32 mentioned it is situation dependent)
My reason for having it separate is our app source code has heavy restrictions around it, and audited regularly. There must be code reviews + app build deploy is triggered any time a merge happens.
Having a separate repo allows me to add automation at my own pace and merge code without a peer review (team of 2 testers). The challenges with separating were finding ways to kick off our automation runs after code deployments, and providing feedback on the main applications pull requests about the automation run statuses. We found a path forward but it requires a lot more effort to get us there.
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email firstname.lastname@example.org.