How to collaborate on Construct projects with GitHub

UpvoteUpvote 56 DownvoteDownvote

Index

Features on these Courses

Stats

23,892 visits, 66,765 views

Tools

Translations

This tutorial hasn't been translated.

License

This tutorial is licensed under CC BY 4.0. Please refer to the license text if you wish to reuse, share or remix the content contained within this tutorial.

Published on 1 Apr, 2020. Last updated 29 Jan, 2025

Modifying the project in Construct

Go back to your project and make a change. For demonstration purposes, we'll add a new Player sprite to our new empty project. Save the project so the files in your project folder update.

Go back to GitHub Desktop. It now lists those changes. There will be a mix of files added (such as the player image) and changed (such as the layout, which now includes a new player instance).

Note that as you select the files on the left, you can see a preview of what changed. It can show image files added, and also the sections of text files that have changed.

It's a good idea to use this preview to double-check your changes are what you expect and that you haven't made a mistake.

Then as before follow these steps to push the changes to the server:

  1. Enter a summary (like Added Player object), and ideally a description
  2. Click Commit to master
  3. Click Push origin to send the commit to the server

As before you can now reload the web page for your repository and see the changes, such as browsing to newly added files. This also means the changes are available for your other team-mates to receive.

There are lots of useful tools on the GitHub website for your repository too. You can review the commit history and see a full list of all changes; see the files changed in each commit; add documentation like a README file; open issues; use project boards and a wiki; and lots more. Refer to GitHub's help for all the details, we're just covering the basic usage here!

  • 20 Comments

  • Order by
Want to leave a comment? Login or Register an account!
  • I've been waiting for this. Thank you finally!!

  • Very useful tutorial. For those who prefer a video tutorial, I've made one here.

    youtu.be/DpCbrGgRkY0

  • As a solo dev hesitant to jump into source control, your tutorial was a game-changer! Now I'm excited to finally integrate it into my workflow and open the door to future collaboration. Thanks for making it so approachable!

  • Very useful and succinct tutorial on using source control via GitHub. thank you.

  • Very cool, when using this though, if I modify the position of an object or add new object etc, changes appear in my GIT commit list. However if I change a tilemap, adding or removing tiles, those changes do not appear in the commit list.

      • [-] [+]
      • UpvoteUpvote 2 DownvoteDownvote
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 2 points
      • (3 children)

      All changes should appear in your commit list. If changes do not appear, then you have not saved the project, and the changes won't be there when you next open the project either.

      • I've tested a few times, certainly saving the project - if I move an object and save, it appears. If I modify a tilemap and save then nothing appears in the commit list.

        What's interesting is if I edit the tile map and then do something like move an objects position, when I commit the changes the tile map edits are saved. So that data is being captured, its just if I edit the tilemap and do nothing else, git thinks I've made no edits to the project and nothing appears in the commit list.

          • [-] [+]
          • UpvoteUpvote 0 DownvoteDownvote
          • Ashley's avatar
          • Ashley
          • Construct Team Founder
          • 0 points
          • *
          • (0 children)

          Tilemap data is saved in the corresponding layout JSON file, so check for changes there. Maybe GitHub Desktop isn't checking there or something, or perhaps you forgot to add the files in the first place.

      • Recorded a quick video showing the issue: youtu.be/QRjykEozW-U

  • Load more comments (11 replies)