mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-02-02 06:19:58 +00:00
56b67085d0
This pull request updates the `.github/workflows/pr-update-playwright-expectations.yaml` workflow to improve how changed Playwright snapshot files are detected and handled, ensuring that both tracked and untracked (new) files are included throughout the process. The changes also add robustness to file operations and improve the accuracy of change summaries. **Improvements to snapshot detection and staging:** * The workflow now detects both tracked and untracked (new) snapshot files in `browser_tests/` when preparing changed files for staging, ensuring that new snapshots are not missed. * When copying changed files to the staging directory, the script now skips files that no longer exist (e.g., deleted files), preventing errors and unnecessary operations. **Enhancements to change summary and commit logic:** * The summary of changes now includes both tracked and untracked files in `browser_tests/`, and the output is expanded to show up to 50 files for better visibility. * The logic for determining whether there are changes to commit now checks for both tracked and untracked changes, ensuring commits are only made when necessary. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-7423-Fix-snapshot-updates-commit-stage-2c76d73d36508195914ec92f37937e67) by [Unito](https://www.unito.io)
GitHub Workflows
Naming Convention
Workflow files follow a consistent naming pattern: <prefix>-<descriptive-name>.yaml
Category Prefixes
| Prefix | Purpose | Example |
|---|---|---|
ci- |
Testing, linting, validation | ci-tests-e2e.yaml |
release- |
Version management, publishing | release-version-bump.yaml |
pr- |
PR automation (triggered by labels) | pr-claude-review.yaml |
api- |
External Api type generation | api-update-registry-api-types.yaml |
i18n- |
Internationalization updates | i18n-update-core.yaml |
Documentation
Each workflow file contains comments explaining its purpose, triggers, and behavior. For specific details about what each workflow does, refer to the comments at the top of each .yaml file.
For GitHub Actions documentation, see Events that trigger workflows.