Repository navigation
ci: add visual regression checks for Gitea 1.27 and 28 - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI previously linted, built and packaged the theme without checking the rendered UI. Add a visual regression matrix on Gitea 1.27.3 and 28.2.0, and require both jobs to pass before the build/package/release job runs.
Each job builds the approved v0.2.2 commit and the candidate, installs their complete packages into two disposable Gitea containers, and seeds identical data through the API. Playwright renders both in the same browser/OS and compares their screenshots; the approved source revision is pinned explicitly rather than following the PR base automatically. Intentional visual changes require an explicit baseline update.
Coverage:
Validation:
GitHub Actions verification: run 41414717706 passed both visual jobs and the dependent build/package job on commit
533fe94. Downloaded and checked both CI artifacts: 56 passed cases, 80 reference/actual screenshot comparisons, no skipped/flaky cases, HTML reports and both Gitea logs. The earlier failed run also verified that build/package is blocked while visual jobs fail and reports still upload.