mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-07-18 01:38:03 +00:00
4d774bfa99
- Deploy job now triggers on both 'success' and 'failure' conclusions of CI: Tests E2E on main, so a failing run's report is still published to the persistent dashboard URL instead of being silently skipped. - Switch the dashboard-deploy concurrency group to cancel-in-progress: false, matching GitHub's recommended Pages deploy pattern — cancelling a deploy-pages run mid-flight can leave a deployment in a bad state, and these deploys are idempotent/infrequent. - Relabel the Playwright report link "Merged chromium E2E report" since the linked playwright-report-chromium artifact only covers the merged chromium-sharded run, not the chromium-2x/chromium-0.5x/mobile-chrome/ cloud projects, which upload as separate artifacts. Addresses review feedback from Christian Byrne on PR #13735. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L5Z1u8a5jspDCYRF4x5WJy
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.