GitGitHubSublime

GitHub: https://github.com/noeespino/dbql_collect

🧠 1. Conceptual foundation (what you’re actually doing)

When you “push code to GitHub,” you’re working with three layers:

🔹 1. Sublime Text

Your editor → where you write code

🔹 2. Git

Your version control engine → tracks changes locally

🔹 3. GitHub

Your remote repository → stores your code online

🔹 4. GitSavvy

A bridge → lets Sublime control Git


👉 Think of it like this:

Sublime → Git (local) → GitHub (remote)

⚙️ 2. Installing Git (Windows)
Step-by-step
  1. Download Git
  2. Run installer
  3. Important option:
    • Select: Git from the command line and also from 3rd-party software

👉 This ensures Sublime can use Git


Verify installation

Open Command Prompt:

git --version

Configure identity
git config --global user.name "Your Name"
git config --global user.email "[email protected]"

🔐 3. Connect Git to GitHub (SSH)

This is authentication.

Generate key
ssh-keygen -t ed25519 -C "[email protected]"
Add key to GitHub
type %USERPROFILE%\.ssh\id_ed25519.pub

Paste into GitHub → Settings → SSH keys


Test
ssh -T [email protected]

Expected:

Hi username! You've successfully authenticated...

🧩 4. Install GitSavvy in Sublime

Inside Sublime Text:

  1. Ctrl + Shift + P
  2. Package Control: Install Package
  3. Install → GitSavvy

📁 5. Initialize your project

Open your folder in Sublime:

File → Open Folder

Then:

Ctrl + Shift + P → Git: Init

🌐 6. Connect to GitHub repo

Create repo on GitHub (empty)

Then in Sublime:

Ctrl + Shift + P → Git: Add Remote
  • Name: origin
  • URL:
[email protected]:your-username/repo.git

🔄 7. The Git workflow (core concept)

Every push follows this sequence:

Step 1 — Add (stage files)
Git: Add

Select . → means all files


Step 2 — Commit (save snapshot)
Git: Commit

Write message:

Initial commit

Confirm:

Ctrl + Enter

Step 3 — Push (send to GitHub)
Git: Push

🧠 8. What each step means (academic clarity)
StepMeaning
AddSelect files for tracking
CommitCreate a version snapshot
PushUpload snapshot to GitHub

🔍 9. Typical errors (and why they happen)
❌ “Nothing to commit”

→ You didn’t stage files


❌ “Detached HEAD”

→ You’re not on a branch


❌ “Permission denied”

→ SSH not configured


❌ “Create fork”

→ You don’t own the repo


🔁 10. Daily workflow (what professionals do)

Inside Sublime:

a → add
c → commit
p → push

🧠 11. Best practices
  • Commit often (small logical changes)
  • Use meaningful messages: Add DBQL parser
    Fix log parsing bug
    Refactor script structure
  • Avoid committing unnecessary files (.log, temp files)

🚀 Final mental model

You are building a timeline of your code:

Edit → Add → Commit → Push → History

🎓 Closing insight
  • Git = memory of your project
  • GitHub = collaboration + backup
  • GitSavvy = productivity interface

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *