Everyday Workflow
This guide walks through a normal day with Checkpoint: getting a workspace, pulling the latest, editing, submitting, and undoing mistakes. Each task shows the desktop app and the chk command line. Both talk to the same daemon, so you can switch between them at any time.
Ignoring Files
Most projects produce files that should never be submitted: build output, editor caches, logs, and local settings. A .chkignore file tells Checkpoint to leave them out. It works like Git's .gitignore.
Branches and Merging
Branches let you keep work apart from the main line of development until it is ready: a risky feature, a release you are stabilizing, or an experiment you may throw away. This guide covers creating and switching branches, merging them back, merge requests, changelist reviews, labels, and what happens when a branch is archived or deleted.
Team Sync
Team Sync is a workspace view in the desktop app for teams that want everyone on a known-good build. If you have used UnrealGameSync (UGS) with Perforce, it will feel familiar: browse changelists with their CI results, sync to any of them, pull down precompiled binaries instead of building, run local build steps, and leave votes and comments for the team.
Linked repos
Linked repos let one repository pin other repositories in the same organization at an exact changelist. When you sync the parent with Team Sync, Team Sync first brings each linked workspace to the changelist the parent pins, then syncs the parent.
Artifacts and CI
Checkpoint gives your CI system two ways to report back on a changelist:
Issue trackers
Each repository chooses where its issues live: Checkpoint's built-in issues, an external tracker, or nowhere. With an external tracker, the repository's Issues tab lists that tracker's issues, and issue references in changelist messages and merge requests link straight to them.