mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-16 10:29:36 +00:00
4d91b745c7
Backport of #11568 to `core/1.43`. ## Changes Applies the e2e workflow filtering changes from #11568 to the `core/1.43` release branch: - **ci-tests-e2e.yaml**: Removed `paths-ignore` from `pull_request` trigger, added `changes` job using `dorny/paths-filter` to detect e2e-relevant file changes, added `needs: changes` and `should_run` conditions to `setup`, `merge-reports`, `comment-on-pr-start`, and `deploy-and-comment` jobs. - **ci-tests-e2e-forks.yaml**: Switched `download-artifact` from `actions/download-artifact@v7` to `dawidd6/action-download-artifact@v12`, added `if_no_artifact_found: warn`, added `hashFiles('reports/**') != ''` condition to `Handle Test Completion`. - **ci-tests-e2e-coverage.yaml**: Skipped — file does not exist on `core/1.43`. ## Conflict Resolution - Kept `core/1.43` branch's existing structure: container image `0.0.16`, cloud build steps, `cloud` browser matrix entry, `Get PR Number` step (not `resolve-pr-from-workflow-run`), `pnpm/action-setup@v4.4.0`. - Applied only the PR's intended behavioral changes on top. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-11592-backport-core-1-43-ci-filter-e2e-workflow-on-PRs-to-skip-unrelated-changes-34c6d73d36508158ac90c13b298132fb) 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.