Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow updating goldens on CI #121

Merged
merged 1 commit into from
Sep 10, 2024
Merged

feat: allow updating goldens on CI #121

merged 1 commit into from
Sep 10, 2024

Conversation

btrautmann
Copy link
Contributor

@btrautmann btrautmann commented Sep 10, 2024

Description

As part of #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

  • ✨ 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)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@btrautmann btrautmann merged commit a36cf47 into main Sep 10, 2024
3 checks passed
@btrautmann btrautmann deleted the bt/update-goldens branch September 10, 2024 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants