mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-27 08:25:50 +00:00
3e710e9ce3
Backport of #11568 and #11587 to `cloud/1.42`. ## Changes **From #11568 (filter e2e workflow):** - `ci-tests-e2e.yaml`: Replace `paths-ignore` on `pull_request` trigger with a `changes` job using `dorny/paths-filter` to skip e2e when only docs/apps/storybook/markdown files change. All downstream jobs gated on `should_run`. - `ci-tests-e2e-forks.yaml`: Switch download action to `dawidd6/action-download-artifact@v12` with regexp name matching and `if_no_artifact_found: warn`. Add `hashFiles` guard to Handle Test Completion step. **From #11587 (e2e-status gate):** - `ci-tests-e2e.yaml`: Add `e2e-status` gate job that consolidates sharded + browser test results into a single required check, so PRs with no e2e-relevant changes aren't stuck waiting. ## cloud/1.42-specific adaptations - Container image: `0.0.13` (not `0.0.16`) - No cloud build step or `cloud` browser in matrix - Browser matrix: `[chromium-2x, chromium-0.5x, mobile-chrome]` - No coverage collection or upload - pnpm-action-setup: `v4.2.0` pin (not `v4.4.0`) - No `merge_group` trigger - Forks file keeps `actions/github-script@v8` PR lookup (not `resolve-pr-from-workflow-run` action) - No `ci-tests-e2e-coverage.yaml` created ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-11594-backport-cloud-1-42-ci-filter-e2e-workflow-add-e2e-status-gate-34c6d73d3650817c91bef7993f8ba575) by [Unito](https://www.unito.io) --------- Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: GitHub Action <action@github.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.