Git & Version Control
Welcome to the Git documentation for the NetSuite development team. This section covers everything you need to know about using Git with VS Code for effective team collaboration.
What This Section Covers
User Guide
- Git User Guide - Complete VS Code Git interface guide for beginners
- Step-by-step workflows for common tasks
- Understanding branches, commits, and pull requests
Commands Reference
- Git Commands Reference - Complete command reference with VS Code equivalents
- Terminal commands for every scenario
- Quick reference cards
Workflows
- Git Workflows - Branching strategies and team workflows
- Feature development process
- Bug fix and hotfix procedures
- Code review process
Troubleshooting
- Git Troubleshooting - Common problems and solutions
- Authentication issues
- Merge conflict resolution
- Recovery from mistakes
Branch Strategy Overview
Our team uses the following branch structure:
main ─────────────────────────────────────────────────────► Production
│ ▲
│ │ (hotfix)
▼ │
develop ──────────────────────────────────────────────────────► Integration
│ ▲ ▲
│ │ │
│ feature/NS-123-new-feature ──────────┘ │
│ │
│ bugfix/NS-456-fix-issue ────────────────────────┘
Branch Types
| Branch | Purpose | Rule |
|---|---|---|
main | Production code - what's live in NetSuite | NEVER push directly |
develop | Integration testing - combines everyone's work | Merge via Pull Request only |
feature/* | Your working branches for new features | Create from develop, merge back to develop |
bugfix/* | Your working branches for bug fixes | Create from develop, merge back to develop |
hotfix/* | Emergency production fixes | Create from main, merge to main AND develop |
Quick Start
First Time Setup
- Install Git - Download from git-scm.com
- Configure your identity:
git config --global user.name "Your Full Name"
git config --global user.email "your.email@company.com" - Clone the repository - See User Guide for detailed steps
Daily Workflow
# Start of day - get latest code
git checkout develop
git pull origin develop
# Create your feature branch
git checkout -b feature/vendor-NS123-description
# Work, commit, push
git add .
git commit -m "[NS-123] Your change description"
git push -u origin feature/vendor-NS123-description
# Create Pull Request on GitHub
Golden Rules
- NEVER push directly to
mainordevelop - ALWAYS pull before starting new work
- ALWAYS create a branch for your changes
- Commit often with meaningful messages
- Push your branch daily (backup!)
- When in doubt, ASK before acting!
Need Help?
- Check the Git Troubleshooting section for common issues
- Review the Git Commands Reference for quick command lookup
- Contact IT Lead for repository access or complex issues