mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-12 00:42:03 +00:00
9c0edd0048
## Summary Fix duplicate `CI: Website E2E` workflow runs on pull requests. ## Problem Two runs were triggered for every PR touching website files: - `website-e2e (pull_request)` — from the PR event - `website-e2e (push)` — from the push to a `website/*` branch The concurrency key used `github.ref`, which evaluates differently for push (`refs/heads/...`) vs pull_request (`refs/pull/N/merge`), so they couldn't cancel each other. ## Changes 1. Scope `push` trigger to `main` only (removes `website/*`) 2. Use `github.head_ref || github.ref` in the concurrency group so push and PR events for the same branch share a group ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-11607-fix-prevent-duplicate-website-e2e-CI-runs-on-PRs-34c6d73d3650814c9d24c77b1591e94a) 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.