Ah thank you, that makes good sense.
When I saw the generated comment I assumed it was that; so to make the flow clearer I would add documentation that explains how comments can specify particulars for an addon, and some examples of common or peculiar user flows. My ideal would be to have this reduce complexity rather than add it (I’m terrible at remembering CLI commands), so in practice that would mean trusting only the
ofPackageManager install command to get everything prepared for a project. For example in an addons.make like this:
local_addons/ofxC # @4f0e76
local_addons/ofxD # https://github.com/user/ofxD
local_addons/ofxE # https://github.com/user/ofxE@2f0e63
It would be awesome to have the CLI do:
ofxA > search for ofxA in addons folder, if not found run http search feature
ofxB > search for ofxB in addons folder, if not found run http search feature, copy locally
ofxC > search for ofxC in addons folder, if not found run http search feature, attempts clone at @commit, defaults to master HEAD
ofxC > clones locally
ofxD > clones locally
I hope this is not requesting more complex features, but rather my perspective is that the wizard structure works really nicely, so on this basis it is addons.make that defines things, followed by ofPackageManager handling them - and the rest of the CLI commands for special cases.