mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-01-30 21:09:53 +00:00
d372cd1d02
Update all CI workflow names to follow "CI: <Description>" pattern for 1:1 correspondence with filenames as suggested by @benceruleanlu: - ci-json-validation.yaml → "CI: JSON Validation" - ci-lint-format.yaml → "CI: Lint Format" - ci-python-validation.yaml → "CI: Python Validation" - ci-tests-e2e.yaml → "CI: Tests E2E" - ci-tests-unit.yaml → "CI: Tests Unit" - ci-tests-storybook.yaml → "CI: Tests Storybook" - ci-tests-*-forks.yaml → "CI: Tests * Forks" Also added explanation of JSON validation scope (all .json files except tsconfig*.json) to address reviewer question. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.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 |
types- |
TypeScript type generation | types-registry-api.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.