Guide: Automagically package and publish addons
View Single Post
10-25-18, 08:17 AM
A Pyroguard Emberseer
Join Date: Feb 2007
Originally Posted by
It relates back to Google Code and SVN days. When Google Code closed there was an option to move all of it to Github which I did.
That is why there is one huge mono repo for all of it.
Never saw a reason to change that.
Git is not SVN, and monolithic repositories comes with a large amount of issues, especially when you want to expand upon just tracking history.
If you ever want to manage dependencies, external tooling, collaboration, or versioning (just to name a few), monorepos is going to become a problem, fast.
My suggestion to you is to spend some time splitting up your single repo into multiple, preferably one per addon, then you'll be able to fully utilize Git as it was intended, which includes being able to use the packager with TravisCI in an automated fashion.
Example of splitting while preserving history:
Last edited by p3lim : 10-25-18 at
View Public Profile
Send a private message to p3lim
Find More Posts by p3lim