Git Experience
Version control and CI/CD workflows for every project, solo or team.
Overview
How I've used Git
Git underlies the workflow for every project I ship, including this portfolio — proper version control isn't optional even on solo projects, because it's what makes safe experimentation and clean rollbacks possible.
This site's deployment pipeline is a direct demonstration: a GitHub Actions workflow builds and tests on every push to main, then deploys over SSH to a self-managed VPS running PM2 — no manual file uploads, no FTP. On client projects, Git discipline shows up as clean commit history, feature branches for anything riskier than a typo fix, and never force-pushing over a deploy that's already live.
What I can do
Specific Git capabilities
- ✓Branching strategies — feature branches, trunk-based workflows depending on project size
- ✓GitHub Actions CI/CD pipelines for automated build + deploy
- ✓Code review practices on collaborative projects
- ✓Safe rollback and hotfix workflows for production issues
- ✓Managing deploy keys and SSH-based server access securely
FAQ
Common questions about my Git work
How do you deploy projects to production?+
For this site and similar projects: push to GitHub, a GitHub Actions workflow runs the build, then deploys over SSH to the VPS and restarts the process via PM2. Fully automated, no manual steps.