As part of https://github.com/Betterment/alchemist/pull/118, we need to re-generate some goldens due to issues with Flutter 3.16 compatibility with existing goldens. See discussions on #103 and #104. However, generating these locally on MacOS to be used by CI does not re-generate all of them, indicating a difference between MacOS and Linux results (this is commented on here).
This PR adds a workflow that would allow maintainers to run a workflow to re-generate goldens on a given branch. The branch input is validated as part of the workflow.
RE: who has access to this button, see here. Basically, collaborators have access to this button, which I think is OK. We also ensure we're not updating main, giving extra safety.
You can see a successful run here which just so happened to run on my 3.16.0 PR and re-generate the correct goldens as shown here.
Type of Change
[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
Description
As part of https://github.com/Betterment/alchemist/pull/118, we need to re-generate some goldens due to issues with Flutter 3.16 compatibility with existing goldens. See discussions on #103 and #104. However, generating these locally on MacOS to be used by CI does not re-generate all of them, indicating a difference between MacOS and Linux results (this is commented on here).
This PR adds a workflow that would allow maintainers to run a workflow to re-generate goldens on a given branch. The branch input is validated as part of the workflow.
RE: who has access to this button, see here. Basically, collaborators have access to this button, which I think is OK. We also ensure we're not updating
main, giving extra safety.You can see a successful run here which just so happened to run on my 3.16.0 PR and re-generate the correct goldens as shown here.
Type of Change