[realcopacetic]

Help, I'm struggling a bit to get my head around how to build and then update a simple repository for my skin. 

I've read the wiki page and some forum posts and think I understand how to manually create a repo with my skin in it. But what I don't quite understand is...

My skin lives on Github here: https://github.com/realcopacetic/skin.copacetic

Is there a way to have a 'live' connection between the repo and the skin, for want of a better word? So when I push an update to the skin files, the repo automatically updates? If I did it manually, I think this would entail updating the skin, downloading the zip, then adding the new zip to the repo manually and removing the old version. Is this the correct methodology?

[kcook_shield]

I'm no expert, and have only recently setup a repository. I used the example at:

https://github.com/drinfernoo/repository.example

Then using _repo_generator.py as noted there can help in updating the repository when you make changes, and in turn the updates will happen for those who have setup your repository and installed your addon(s).

I'm sure others here can be of more help, but using this example has helped me get started.

[scott967]

Create the new zip file, update addons.xml to reflect the new skin version, and generate a new md5 hash.

scott s.
.

[realcopacetic]

I'm no expert, and have only recently setup a repository. I used the example at:

https://github.com/drinfernoo/repository.example

Then using _repo_generator.py as noted there can help in updating the repository when you make changes, and in turn the updates will happen for those who have setup your repository and installed your addon(s).

I'm sure others here can be of more help, but using this example has helped me get started.

Thanks, this is very helpful! I only used Github desktop before so going into the terminal will be a fun learning experience!

[kcook_shield]

@"QuizKid" 

You can enter the terminal from within Github desktop "Repository" > "Open in command prompt" ;-)

[realcopacetic]

Thanks @kcook_shield - slowly getting there I think!

[realcopacetic]

Create the new zip file, update addons.xml to reflect the new skin version, and generate a new md5 hash.

scott s.
.

Sorry @scott967 could you idiot-proof your explanation please?

I have my repo up and running and I was able to install version 0.5.0 of my skin through it.

The skin is a submodule so I see it as a link in github.com with an id appendage. And clicking it takes me to that version of my skin: https://github.com/realcopacetic/realcop...aster/repo

Great so far. 

Now I've updated my skin and it's one commit ahead. So how do I reflect that change in my repository? Do I need to run through the process of adding the submodule again?

[realcopacetic]

update - I found a good guide here: https://git-scm.com/book/en/v2/Git-Tools-Submodules

It seems you need to be working from a terminal to update a submodule, can't do it in github desktop

[realcopacetic]

One last question before I leave you all alone. Each time I update, the _repo_generator.py tool creates a new zip of my skin in the zip folder. See: https://github.com/realcopacetic/realcop....copacetic

I've seen this can get very big for example in @jurialmunkey's repo: https://github.com/jurialmunkey/reposito....horizon.2

Are there rules or best practices on culling the older ones?

[wsnipex]

that's not a big list at all. Usually you wouldn't remove old versions

[realcopacetic]

that's not a big list at all. Usually you wouldn't remove old versions

Ok thanks!