Posted July 16, 2018
I'm working on the built in update option at the moment.
Not sure when I'm going to roll it out but when I do the repo structure will change a bit.
Dev branch will be retired unless I'm messing with stuff that I think is particularly likely to nuke a manifest or something.
The master branch repo's files will be a rolling update kind of thing (so latest features but may bork stuff sometimes), I will endeavour to test stuff.
I'll be issuing releases which will become the standard build, at that point.
gogrepoc will have an auto-updater included and I'll have some stuff where you can decided if you want standard/rolling/no auto-updates (useful for people who want to do dev work so running the script doesn't nuke your changes, I'll put in a manual option for testing for that case too).
Not sure when I'm going to roll it out but when I do the repo structure will change a bit.
Dev branch will be retired unless I'm messing with stuff that I think is particularly likely to nuke a manifest or something.
The master branch repo's files will be a rolling update kind of thing (so latest features but may bork stuff sometimes), I will endeavour to test stuff.
I'll be issuing releases which will become the standard build, at that point.
gogrepoc will have an auto-updater included and I'll have some stuff where you can decided if you want standard/rolling/no auto-updates (useful for people who want to do dev work so running the script doesn't nuke your changes, I'll put in a manual option for testing for that case too).