Documentation Index
Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Summer can commit locally right away, but most users should connect their project to GitHub early. That gives you backups, a shared source of truth, and a safer workflow when you start committing often. The simplest flow is:- Create an empty repository on GitHub
- Copy the repository URL
- Paste that URL into Summer chat
- Ask Summer to connect the current project to that repository
- Use the
Changesdock to commit, push, and sync
Before You Start
Make sure:- Git is installed on your machine
- Your Summer project already exists locally
- You are signed in to GitHub in the browser if you plan to use an HTTPS remote
Step 1: Create An Empty GitHub Repository
Open GitHub and create a new repository. Recommended settings:- Choose a repository name that matches your project
- Keep it empty if the project already exists locally
- Do not add a README,
.gitignore, or license during creation
Step 2: Copy The Repository URL
After the repository is created, copy the repository URL from GitHub. HTTPS is usually the easiest option for most users:Step 3: Ask Summer To Connect The Project
Open your project in Summer. Then open chat and paste the repository URL with a clear instruction, for example:Step 4: Verify The Connection In The Changes Dock
Once the remote is connected, open theChanges dock.
You should now see a GitHub-backed workflow instead of a local-only state.
Useful things to look for:
- Your branch name
- Sync state when the branch is ahead or behind
- Commit and push behavior tied to the remote repository
- Graph history that reflects normal user-facing Git history
Step 5: Commit And Push
After the project is connected:- Make a change in your project
- Open the
Changesdock - Review the changed files
- Enter a commit message
- Commit
- Push or sync if Summer shows outgoing changes
Understanding The Changes Dock
TheChanges dock shows the current working tree.
Common status letters:
M: modifiedU: untrackedA: addedD: deletedR: renamed
- Hover a file row to open, discard, stage, or unstage it
- Deleted files appear with a strikethrough and a
D - If your branch is ahead or behind, Summer shows a sync action instead of a normal empty state
Understanding Sync
If Summer shows arrows such as2↑ or 1↓, that means your branch and the remote are out of sync.
↑means your local branch has commits that are not on the remote yet↓means the remote has commits that are not on your machine yet
Best Practice
For a smooth workflow:- Connect to GitHub early
- Keep the first GitHub repository empty if the project already exists locally
- Commit often
- Push regularly
- Sync before continuing if you are behind

