mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-13 17:26:22 +00:00
50cb16fb07
- Add explicit permissions (contents:write, pull-requests:read) to update-screenshots job - Move all expression interpolations in github-script blocks to env vars to prevent expression injection - Move permissions from workflow-level to job-level in preview workflow - Rename post-status-comment to post-result-comment for consistency - Rename generic 'Build section content' steps to be workflow-specific - Replace paginate with listComments + per_page:100 - Guard against null comment body with ?? '' - Document comment-marker, section names, escapeRegex, and is-pr output Amp-Thread-ID: https://ampcode.com/threads/T-019db842-342c-7307-ae60-14e6f3a24b8e 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.