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.
You don't need to understand Construct's JSON format for saving files. However you'll probably start to recognise what kinds of changes affect different files over time as you work on your project.
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:
- Enter a summary (likeAdded Player object), and ideally a description
- ClickCommit to master
- ClickPush 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 toGitHub's help for all the details, we're just covering the basic usage here!