Add CI check for uncommitted changes after build

[Copilot]

Done

• Added CI step in test-python job to detect uncommitted changes after yarn build
• Check fails if build process creates uncommitted files (indicates gitignore misconfiguration or missing commits)

QA

• Check out this feature branch
• Run the site using the command ./run serve
• View the site locally in your web browser at: http://0.0.0.0:8002/
• Run through the following QA steps
• Verify that yarn build produces no uncommitted files (all generated assets are gitignored)
• Verify PR checks pass in GitHub Actions

Screenshots

N/A - CI/CD workflow change only

[!WARNING]

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• googlechromelabs.github.io
  • Triggering command: /usr/local/bin/node /usr/local/bin/node install.mjs (dns block)
• https://storage.googleapis.com/chrome-for-testing-public/143.0.7499.42/linux64/chrome-linux64.zip
  • Triggering command: /usr/local/bin/node /usr/local/bin/node install.mjs (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Cancel: "Uncommitted changes detected"

Created from VS Code via the GitHub Pull Request extension.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.