Question - Updating KA ini files using source repository

[Naturesong]

Hi all,

Looking for a strategy for updating my published KA ini's using git hub.

Current state:
Kiss Assist ini's for multiple classes published in 5 level increments.
All contain a preamble of relevant notes etc as well as the

Code Block

.
All are updated manually.

Desired State:
Kiss Assist ini's for multiple classes published in 5 level increments.
For all ini's to still contain a preamble of relevant notes etc as well as the code block.
Any changes to my git repo that I push to my github account automatically update the ini's published here.

Knowledge gap:
Confirmation that I need to purchase a connector from the RG store.
How to markup the source files to ensure that the file published on RG retains the format of the current published ini's
Migration of current published ini's ... is it just a matter of pointing to the current inis to the new source?
Design of the git repo itself ... as I have multiple classes, each with multiple releases should I do one repo per class, and branch every 5 levels?
Can I add RedGuides as a collaborator to my repo's in gitHub? (this ensures my repo's are not public, but gives visability so the ini's here can be updated)
There's a good chance that I'm missing something or have a fundamental misunderstanding somewhere - if you think I have based on my questions, please poke at it.

I'm not a programmer (dabbled a bit with C#, SQL, Bash, PowerShell) but I have used various VCS's over the years, including git. I have a gitHub account and use git primarily for study and personal projects (now that I'm no longer working in IT) so I have enough knowledge to get myself into trouble.

Any pointers or even questions that may help me to explore my understanding of the problem domain would be very welcome.

 

[Sic]

I don't think the library would currently allow you to do that, but let me tag in @Redbot

 

[Redbot]

The kissassist ini library is currently set up to display configurations in code blocks, so users can quickly copy & paste relevant parts.

To automate with git as a backend, like we do with some other resources, would require us to store kiss .ini files as downloadable files. That will probably happen in the near future, but not right now.

 

[Naturesong]

Cheers for the prompt response.
I'll start setting up the repo now anyway as the amount of ini's and relevant notes is getting bit out of hand.

 

[manydills]

I strongly support this effort! I've been a huge fan of your .inis since I discovered them.

 

[Naturesong]

I strongly support this effort! I've been a huge fan of your .inis since I discovered them.

Thank you.

Been a small delay in progress as I've been doing epics and tradeskills recently - and work.
Current ones do have a few errors which I'm going through and updating when I can, and I'm about to start the next group (Shadow Knight, Druid, berserker, Necro and Ranger).
Hence the desire to start getting them into version control, and with that reduce the overhead of manually amending the ini's here when I find an error or find a better way to achieve the result I've after.