Skip to content

ci: add a daily cleanup of the gh-pages previews - #2719

Open
matyasf wants to merge 1 commit into
masterfrom
gh_pages_cron_cleanup
Open

matyasf wants to merge 1 commit into
masterfrom
gh_pages_cron_cleanup

Conversation

@matyasf

@matyasf matyasf commented Sep 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a scheduled workflow (daily, 03:00 UTC) that removes pr-preview/pr-N and visual-regression/pr-N folders from gh-pages when their PR is merged, closed, or gone
  • An API error keeps the folder; removals go in one commit; the push retries from a fresh tip if another workflow moved the branch

Test Plan

  • After merge, check the first scheduled run's log: every listed folder should belong to a merged, closed, or missing PR, and no open PR's folder should be touched
  • Compare git ls-tree origin/gh-pages pr-preview/ visual-regression/ before and after that run

🤖 Generated with Claude Code

@matyasf matyasf self-assigned this Sep 16, 2026
@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://instructure.design/pr-preview/pr-2719/

Built to branch gh-pages at 2026-09-16 13:22 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@github-actions

github-actions Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Visual regression report

Cypress suite: ✅ Passing

Visual diff: ⚠️ Changes detected.

Status Count
Unchanged 92
Changed 4
New 0
Removed 0

Accessibility (axe): ✅ No violations.

📊 View full report — click a screenshot's ⚠ badge to see each violation boxed on the image, with the offending element named and contrast failures shown as color swatches.

Diff images (4)

badge-canvas.png — 1573 pixels differ

calendar-canvas.png — 478 pixels differ

tooltip-dark.png — 881 pixels differ

tooltip-light.png — 956 pixels differ

Baselines come from the visual-baselines branch. They refresh on every merge to master. The Cypress suite line covers the a11y and console-error assertions — a ❌ there means the suite found real issues even if the visual diff is clean.

github-actions Bot pushed a commit that referenced this pull request Sep 16, 2026
matyasf added a commit that referenced this pull request Sep 16, 2026
The daily cleanup in gh-pages-cleanup.yml (PR #2719) owns removal of closed-PR folders, so the
close-event cleanup job and the retrying push script are not needed. What remains fixes a
different bug: the repo-wide `gh-pages` concurrency group cancelled other PRs' queued
visual-regression runs, so those PRs got no report for that commit.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@matyasf matyasf changed the title ci: add a daily cleanup of closed-PR folders on gh-pages ci: add a daily cleanup the gh-pages previews Sep 16, 2026
@matyasf
matyasf force-pushed the gh_pages_cron_cleanup branch 2 times, most recently from 6595e70 to 99b2a33 Compare September 16, 2026 13:15
@matyasf matyasf changed the title ci: add a daily cleanup the gh-pages previews ci: add a daily cleanup of the gh-pages previews Sep 16, 2026
The new scheduled workflow shallow-clones gh-pages once a day, asks the API for the state of every
pr-N folder under pr-preview/ and visual-regression/, and removes the folders of merged, closed and
missing PRs in one commit. An API error keeps the folder. The push retries from a fresh tip when
another workflow moved the branch in the meantime.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@matyasf
matyasf force-pushed the gh_pages_cron_cleanup branch from 99b2a33 to 87625be Compare September 16, 2026 13:17
@matyasf
matyasf requested a review from balzss September 16, 2026 13:18
github-actions Bot pushed a commit that referenced this pull request Sep 16, 2026
github-actions Bot pushed a commit that referenced this pull request Sep 16, 2026
@balzss
balzss requested a review from HerrTopi September 18, 2026 10:01
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