mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-27 08:25:50 +00:00
b52d40b431
Backport of #11568 and #11587 to `core/1.42`. ## Changes **From #11568 — filter e2e workflow on PRs:** - Removed `paths-ignore` from `pull_request` trigger (replaced by `changes` job) - Added `changes` job using `dorny/paths-filter` to detect e2e-relevant file changes - Added `needs: changes` + `if: should_run` conditions to `setup`, `merge-reports`, `comment-on-pr-start`, `deploy-and-comment` - Forks workflow: switched to `dawidd6/action-download-artifact@v12` with `if_no_artifact_found: warn` and `hashFiles` guard **From #11587 — e2e-status gate:** - Added `e2e-status` gate job that provides a single required check for branch rulesets ## Adaptations for core/1.42 - No `merge_group` trigger (not used on release branches) - Container image `0.0.13` (not `0.0.16`) - No cloud build step or `cloud` browser matrix entry - No coverage upload steps - Forks file keeps `actions/github-script` PR lookup (not `resolve-pr-from-workflow-run`) - No `ci-tests-e2e-coverage.yaml` (doesn't exist on this branch) ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-11595-backport-core-1-42-ci-filter-e2e-workflow-add-e2e-status-gate-34c6d73d365081f79ee5e8c8f18462d1) by [Unito](https://www.unito.io) Co-authored-by: Amp <amp@ampcode.com>
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.