Skip to content

Conversation

@sunker
Copy link
Contributor

@sunker sunker commented Nov 6, 2025

When Playwright reports are deployed to the gh-pages branch within the same repository, the repository size can grow significantly over time, leading to a bloated Git history. This is especially problematic when reports include trace viewers and screenshots.

This PR introduces a new external-repository input that allows reports to be deployed to a dedicated repository (for example, grafana/playwright-reports), helping keep source repositories lean.

Example where this is used here: grafana/grafana-test-datasource#18

@hugohaggmark hugohaggmark moved this from 📬 Triage to 🧑‍💻 In development in Plugins Platform / Grafana Community Nov 6, 2025
@sunker sunker changed the title (wip) PW reports: Allow deploying to external repo PW reports: Allow deploying to external repo Nov 7, 2025
@sunker sunker changed the title PW reports: Allow deploying to external repo feat: allow deploying to external repo Nov 7, 2025
@sunker sunker force-pushed the pw-gh-pages/deploy-to-another-repo branch from 62b9e70 to 094dba3 Compare November 7, 2025 11:30
@sunker
Copy link
Contributor Author

sunker commented Nov 7, 2025

closing in favour of #181

@sunker sunker closed this Nov 7, 2025
@github-project-automation github-project-automation bot moved this from 🧑‍💻 In development to 🚀 Shipped in Plugins Platform / Grafana Community Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant