Version Controlled Mod tree now available.

from GalCiv3 Forums

Folks, 

I finally got around to setting up a version control repository with the necessary XML files for modding in it, in various branches.

It makes it easier to track releases and community patches, and, ultimately, Mods.

 

It's available here:

https://bitbucket.org/trims/galciv3

 

Right now, it's read only. I'd like to add people to be able to commit and do work on it, but you need an Atlassian Bitbucket account (it's free to sign up).

Please let me know if you guys want me to keep this going, and if we should use this kind of things for a more permanent place to keep our GC3 Mods and potential fixes. Using a DVCS like git is a real good idea for this kind of thing.

 

I put in the things I think we need, and removed the things that we don't. This should fit with StarDock's Mod license, and the various DLC are required before the game can work (i.e. you can't download the files and get the DLC - it's missing enough stuff that they won't work unless you've bought them). 

 

Comments?

14,058 views 4 replies
Reply #1 from GalCiv3 Forums Top

Is it using CVS, SVN, Git, what??

I have been using a local Git repo and had though about pushing it to github, but yours works just as well I guess

Reply #2 from GalCiv3 Forums Top

This is git. 

 

I changed the location, to make it a Team based collaborative area, complete with Issue tracker.

 

https://bitbucket.org/gc3modders/galciv3

 

There's a nice web UI for managing everything.  Also, there's a good Git client for both windows and mac:  SourceTree  (https://www.sourcetreeapp.com/)

 

Also, I populated the project with some possible issues that I'd like to start working on.  Look at them to see how this might work for your own particular issues and enhancements.

The Political Machine 2024
Reply #4 from GalCiv3 Forums Top

I prefer GitLab or Bitbucket over GitHub, for the simple reason that both of them are much more feature-complete. 

GitHub is version control, pull requests, and a lightweight issue tracker.

GitLab and Bitbucket do all that, plus a better issue tracker, build time (which would include stuff like pre-commit testing), test support, etc.  I also like the WebUI of both much better than GitHub's, but that's a personal thing.

In short, GitHub is just the start of the CI toolchain. GitLab and Bitbucket offer the entire chain.