Hacker News new | ask | show | jobs
by paulryanrogers 20 days ago
You still have to track upstream and merge conflicts. Or else you have to get LLMs to fix all the CVEs in your fork.
1 comments

I'm guilty of creating a fork that just goes off the rails, but still needs to keep up with upstream. I do it via a skill and seems to work good enough for now: https://github.com/midasvo/findroid-ce/tree/main/.claude/ski...
I'm doing it right now to see what the cost is; I cloned the upstream and made a copy of the working directory and asked the Qwen3.6-35B-A3B model to merge my production files with the new upstream.

Since it's just a duplicate folder, I can always fall back if it fubars.