Git

Git keeps every saved step of your project, so you can see what changed, go back when something breaks, try ideas out on a branch, and share your code on GitHub or GitLab. The IDE has Git built into it: a Git window for committing, pulling and pushing, change marks beside your code, and a history of every file.



What You Need

The IDE uses Git itself. Most Linux systems have it already; if yours hasn't, the Git window says so. Install it with your package manager (sudo apt install git on Debian and Ubuntu, sudo pacman -S git on Arch), then press Check again. If Git is somewhere unusual, Choose git... points the IDE at it. The IDE runs your own git, so it uses your usual Git settings and logins.

A free GitHub or GitLab account is only needed if you want a copy of your project online.



Where to Find It

Everything is under View > Git:

Right-clicking in the editor has the same file commands. The right-hand end of the status bar shows your Git project, for example Git: main · MyGame ●3 ↑1: the branch, the project, 3 changed files, and 1 commit waiting to be pushed. Click it for the branch menu.



A Few Words First

Choosing a Git Project

The Git window always works on one Git project that you choose. Commit, Pull and Push only cover that project's folder, whatever else you have open in the editor.

If you lock a build file while a project is chosen, the IDE remembers that project for it: locking that file again brings its project back. If you open a file that's in a repository and no project is chosen, the window offers Use this repository. It never picks one by itself.



The Git Window

At the top are the project's name, its folder and its branch, with how many commits are waiting to be pushed or pulled. The Project... button has New Repository, Connect, Recent Projects, History, Open Project Folder, Git Settings and Disconnect.

The box at the bottom shows what Git said, which is the place to look if something didn't work.

Before a commit, pull or branch switch, the IDE offers to save any unsaved files in the project. After a pull, open files that changed are reloaded.



Your Name and the Online Copy

Every commit is signed with a name and email. The first time you commit, the IDE asks for them if Git doesn't have them yet. Project... > Git Settings changes them, for all your repositories or just this one. Remember they're public if you push to a public repository.

Git Settings is also where you set or change the online repository's URL.

Signing in. The IDE can't ask for a password while Git runs, so Git needs a login it can use by itself before you push to (or pull from) a private repository. Set up one of these once, in a terminal:

The IDE never sees or stores your password or token. If a push says Git couldn't sign in, that's the message's cue to set one of these up.



Pushing and Pulling

Change Marks Beside Your Code

For any open file that's in a repository, a thin bar beside the code shows what's changed since the last commit. It updates as you type:

Click a mark to see the old lines next to the new ones. Put the old lines back undoes just that change (or Remove these lines for new ones). Ctrl+Z brings it back. Files Git leaves out (like the generated .cpp) get no marks, and a file that's never been committed shows as all new.

A tab whose file differs from its last commit has a dot after its name: MyGame.bam ●.

Compare with Last Commit shows the whole file side by side with its last commit, lined up and scrolling together, unsaved changes included. Previous change and Next change jump between the differences.

Revert File to Last Commit... (right-click in the editor) puts the whole file back the way it was at the last commit. It happens in the editor, so Ctrl+Z still brings your changes back until you close the file.



History

History (in the Git window, or View > Git) lists the project's commits, newest first. History of This File shows only the commits that changed one file, following it through renames.



Branches

The Branch... button in the Git window (or a click on the Git part of the status bar) opens the branch menu:

If you switch with changes you haven't committed, the IDE asks whether to Commit first or Put them aside (Git calls it a stash). Put-aside changes wait until you choose Bring Back Put-Aside Changes from the branch menu, on whichever branch you like.



When Changes Clash

If a merge (or a pull that merges, or an undo) finds that both sides changed the same lines, Git can't choose between them, so it's up to you:



If Something Goes Wrong

The IDE runs the same Git you'd use in a terminal, so anything you do there (or in another Git program) shows up in the IDE too.


BambooBasic © 2026 Michael Denathorn