Comfy-Org / Comfy-Org/publish-node-action

Create an optionnal comfyignore option to strip unwanted files

Open
#9 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Hello, it is a great action but I think there a lot of boilerplate files not usefull when publishing with this, for example (random custom node I have) :

Image

You can see some tracking changelogs, etc, nothing dangerous BUT it would be great if it we have some kind of mechanism to ignore files if we want.

Some use cases :
- A private repository with workflow we don"t want to share.
- Some custom nodes tests with heavy dependencies inside the project for development only
- Some newbies projects with sensible environment information inside and no gitignore (like the token ? I would guess it have happen)

It would translate for YML (with by default using a file .comfyuiignore) :
```yml
name: Publish to Comfy registry
on:
workflow_dispatch:
push:
branches:
- main
paths:
- "pyproject.toml"

jobs:
publish-node:
name: Publish Custom Node to registry
runs-on: ubuntu-latest
steps:
- name: Check out code
uses: actions/checkout@v4
- name: Publish Custom Node
uses: Comfy-Org/publish-node-action@main
with:
personal_access_token: ${{ secrets.REGISTRY_ACCESS_TOKEN }}
ignore_file: .comfyuiignore # Optional override
```

Maybe would need `comfy-cli` changes too to make it work with an option flag `--ignore-file .comfyuiignore` (there is no documentation about it).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the publish-node-action input handling and the comfy-cli publishing entry point, especially how the workflow's optional ignore_file value could reach the publisher. Define the expected .comfyuiignore path rules and verify that both the GitHub Action input and the proposed --ignore-file flag exclude the intended files without changing default publishing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
cli, devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.