Here’s the sample game running which will serve as our testbed for a GitHub Action-based build: Game Running. Voila, much better! Project Structure Fixed. gitignore but I’m just going to move all of my project files to the root folder of the repository, for ease. This is caused by an extra, nested, folder being created on project initialisation. I’m going to set up for ‘full-force 3D’ and drop a project in our local repository: Big Red Ball Setup.Īt this point, I realise that I have a project setup fail, of sorts, leading to every file in existence getting caught up as a change: Structure Issue. Our concept then is ‘big-red-ball’, the best game about a red ball that we can conjure up in not much time at all. Let’s Build a Great Game (no, not really) The repository name and description will give you a rough idea of what we’re going to create. I’ve made the repository private to protect what will surely be awesome source code (or to save from impending embarrassment). We need a repository and, I didn’t actually know this, but it looks like the standard options for ‘.gitignore’ auto-generated files do include an option for ‘Unity’, so we’ll be selecting that from the get-go. So, as I rest by bum between the chair and keyboard once more my mind wanders to the realm of GitHub Actions does a solution exist in this alternate realm (and, more importantly, will I be able to get it to work!). ![]() I’m clearly missing a trick and, let’s be honest, magically grasping hold of a ‘trick’ at 1am probably isn’t the easiest thing to do. This post has been triggered by a rather long succession of failures to get any kind of build working with Unity 3D using my locally hosted runner with GitLab.
0 Comments
Leave a Reply. |