Skip to content

Inviting @Davidb-2107 to upstream work from the capcut-cli-david forkΒ #36

Description

@renezander030

Hi @Davidb-2107 πŸ‘‹

I came across your capcut-cli-david fork and wanted to reach out. The work looks genuinely useful β€” the create / pipeline / validate and make-preset commands, the per-word caption highlighting, and splitting src/ into clean command modules are all directions I'd like the main tool to go.

Forking is completely fair, and some of your changes may be specific to your setup. But you're ~80 commits ahead of master now, which means you're maintaining all of it against a moving upstream, and no one else gets to use it. If you're open to it, I'd happily review any of it as focused PRs β€” one command at a time is easiest to merge, and I'm glad to help scope them or adapt them to the current structure. Something self-contained like validate would be a natural first one. Even one would be welcome.

If part of the reason you forked was that adding a command meant hacking on a big index.ts, that's fair feedback β€” your command-module refactor is exactly the kind of thing that would make future contributions easier, and I'd be interested in moving upstream in that direction with you.

There's now a CONTRIBUTING guide with the command pattern and PR flow, if it helps.

No pressure either way β€” mostly wanted you to know the door's open and the contributions would be valued.

Thanks for building on it,
Rene

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions