Skip to content

chore: ignore Playwright MCP artifacts at repo root#277

Merged
hokiepokedad2 merged 1 commit into
mainfrom
chore/gitignore-playwright-artifacts
May 22, 2026
Merged

chore: ignore Playwright MCP artifacts at repo root#277
hokiepokedad2 merged 1 commit into
mainfrom
chore/gitignore-playwright-artifacts

Conversation

@hokiepokedad2
Copy link
Copy Markdown
Contributor

Summary

Loose .png screenshots from Playwright MCP runs (login.png, raid-add-dialog-420.png, rsvp-desktop*.png, rsvp-zoom.png) and the .playwright-mcp/ output directory kept showing up as untracked at the repo root, polluting git status between sessions.

Fix

Add two patterns to .gitignore:

  • .playwright-mcp/ — Playwright MCP's persistent output directory
  • /*.png — root-only, so it catches scattered screenshots without touching the tracked PNGs under Applications/Pgan.PoracleWebNet.App/ClientApp/public/assets/help/ and elsewhere

Verified no tracked PNGs exist at the repo root (git ls-files "*.png" | awk -F/ 'NF==1' is empty), so the /*.png rule is safe.

Test plan

  • After merge: git status from a fresh checkout stays clean even with Playwright artifacts present
  • Tracked PNGs under ClientApp/public/assets/ are unaffected (they're not at the repo root)

Loose .png screenshots from Playwright MCP sessions and the `.playwright-mcp/`
output directory keep showing up as untracked at the repo root. None of them
belong in the tree (tracked PNGs all live under
`Applications/Pgan.PoracleWebNet.App/ClientApp/public/assets/`). Add a
root-only `/*.png` rule plus `.playwright-mcp/` so `git status` stays clean.
@github-actions github-actions Bot added the chore label May 22, 2026
@hokiepokedad2 hokiepokedad2 merged commit 8c6287f into main May 22, 2026
6 checks passed
@hokiepokedad2 hokiepokedad2 deleted the chore/gitignore-playwright-artifacts branch May 22, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant