Tooling for a persistent, cross-branch patch series?

[stdedos]

Hello there!

A problem I face all too often:

1. I come up with a useful idea
2. I implement it
3. I propose it upstream
4. It gets declined (fair!)

Thing is, I still need that functionality. For instance, gem 'ricecream' is super helpful in my day-to-day.

Forking isn't really an option - I need to stay close to upstream.
For smaller projects, I keep patches on my master and clean them up before contributing. But in branch-heavy workflows, that gets unmanageable quickly.

I've looked into https://gitbutler.com/ - too heavy and slow, weird branches.
stg sounds promising, but stg init is per-branch, and I need something cross-cutting.

What I really want:

• A persistent patch series, like a "one true patchset"
• It should rebase cleanly, git pull --rebase --autostash-style
• Ideally, I could snapshot it (e.g., OTPS/before-big-bang) and revisit it later (e.g. when developing for an maintenance version)
  • I am fine "fixing it now" and "throwing it away" later

Does such tooling or workflow exist?
Thanks for reading - I appreciate any tips or experiences shared 🌟🌟🌟

[lkraav]

Yeah I think I could use something like this to keep certain Docker Mongo volumes static instead of anonymous aross branches.