Is there an existing issue outlining your problem?
Describe your issue.
We now have a demo instance we can easily spin up. It would be nice if we could use this to generate the example screenshots automatically. I can think of two ways to do this:
- Auto-generate the screenshots as part of the release workflow -- not sure how difficult that will be to integrate into the release-please workflow, especially since we do want the screenshots to end up back in the repo itself. Maybe there's some way to inject the screenshot updates into the release-please PR itself?
- Add a workflow that checks to make sure the screenshots generated by each PR match the ones stored in that PR, and leave a comment if they change. This will ensure that each PR merged updates any affected screenshots, but it also makes it a bit harder to move with any speed as it means almost every PR will end up conflicting in some way.
Even if we go with option 1 I still think it would be nice to at least have a visual regression check as part of the PR process, ideally in a way that leaves a comment on the PR with a visual diff of what changed.
Is there an existing issue outlining your problem?
Describe your issue.
We now have a demo instance we can easily spin up. It would be nice if we could use this to generate the example screenshots automatically. I can think of two ways to do this:
Even if we go with option 1 I still think it would be nice to at least have a visual regression check as part of the PR process, ideally in a way that leaves a comment on the PR with a visual diff of what changed.