Pull latest changes
Keep your branch current before coding. Pull first to reduce integration surprises and catch upstream changes early.
Tutorial 102
Working with repositories and branches
Master pull, commit, push, branch operations, and merge conflict resolution in StarGit. This tutorial is the practical daily workflow guide after installation.
Pull safely
Commit cleanly
Push confidently
Pull, commit, and push
These three operations define your core loop in StarGit.
Commit your work
Stage intentional changes and commit with meaningful messages. StarGit helps you review status and keep commits focused.
Push to remote
Publish your branch so teammates and automation can consume your updates. Prefer clean branch history and clear intent.
Working with branches
Branch workflows let teams ship safely in parallel.
Creating a branch
Create feature-specific branches to isolate work from your stable baseline.
- Create:
git branch <branch-name> - Switch:
git switch <branch-name> - Use meaningful names:
feature/login-page
Switching branches
Move between contexts without losing work. Ensure your current changes are either committed or stashed first.
git switch <branch-name>- Use status checks before switching
- Use stash when needed
Pulling and pushing branch updates
Sync regularly with your remote branch to keep collaboration smooth and reduce large merge bursts.
- Pull:
git pull origin <branch-name> - Push:
git push origin <branch-name> - Set upstream once:
git push -u origin <branch-name>
Merging and conflict resolution
Conflicts are normal. Resolve quickly with a repeatable flow.
- Initiate merge: choose source branch and start merge in StarGit.
- Resolve conflicts: review highlighted files and choose staged resolution.
- Finalize merge: continue merge with a clear commit message.