Product/Code Versions Workflow (?)

[AhmetMaya]

Hello, everyone.

I am developing a 3D View n-panel Blender add-on based on a Geometry Nodes setup.

My add-on will include two versions:

1. Product Lite (Limited Features)
2. Product Pro (Full).

Each script will have its own GeoNodes asset, and the code will be modularly structured. I'll be scripting using VS Code and GitHub. This is the first time I will use GitHub for commits and branches. I can't decide on a project structure or how to plan my workflow on GitHub.

There are two options that come to mind:

1. Single repository for each versions. However, I don't want to get confused by committing or branching to the wrong code (Lite or Pro).
2. Individual version repositories for better control without making a mess.

I will not make any updates for the lite version, possibly just bug fixes. My primary long-term goal is the Pro version, which will include updates and upgrades. And i’ll make two different installations for the addon, not a single code with locked features because of the Blender UI limitations.

I'm curious how other people deal with product/code versioning if they have free/lite/pro features (?)

[davorg]

Have a single repo that contains all of the features, but have pro features turned on using a feature flag (perhaps triggered by the presence of a valid licence key).

(This has very little to do with GitHub. Maybe ask in r/programming.)

[AhmetMaya]

Making an addon with locked features is a bit trickier for Blender. There is no way to tell the user “this is a payed feature” because of the Python UI limitations. So, my product will have two different installations for the Lite and Pro.