0Pricing
Vibe Coding · Pelajaran

Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan

Buat commit, cabang, dan push dengan panduan kecerdasan buatan.

Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan adalah pelajaran Vibe Coding gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Vibe Coding, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Vibe Coding mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

From Theory to Hands-On

Last lesson you learned why version control matters. Now you'll actually use it — and you won't memorize a single command.

Your AI assistant (Cursor, Claude Code, Copilot, or even ChatGPT) will write every Git command for you. Your job is to understand what each step does so you stay in control.

By the end, you'll have made a commit, a branch, and a push. Let's go.

The Four Core Actions

99% of Git work is just four actions:

  • init — start tracking a project (once per project)
  • commit — save a snapshot
  • branch — make a parallel copy to experiment
  • push — upload your snapshots to GitHub

Learn these four and you can build real apps. Everything else you can ask AI for as you need it.

Starting a Project (init)

To begin tracking a folder, you run git init once. Most tools (Cursor, Replit, GitHub Desktop) do this with a button, but here's what it looks like.

Don't type this blindly — paste it into your AI and ask it to confirm. Here's a prompt to do that:

I'm in my project folder in the VS Code terminal.

Walk me through starting Git tracking for this project, step by step.
I think the first command is `git init` -- confirm that, tell me
exactly what to type, and what I should see after each command.

Staging vs Committing

One thing that confuses beginners: before you commit, you stage your changes. Staging means "these are the changes I want in this snapshot."

Two-step rhythm: stage what you want, then commit it with a message.

  • git add . — stage all your changes
  • git commit -m "Add homepage" — save the snapshot

Think of staging as putting items in a box, and committing as sealing and labeling the box.

Your First Commit Prompt

Here's the exact prompt to make your first commit. Paste it into your AI assistant and follow along:

I just built my homepage and it works. I want to save this snapshot.

Give me the exact terminal commands to:
1. Stage all my changes
2. Commit them with the message "Add working homepage"

Then explain what each command did in one sentence.

Seeing Your History

After a few commits, you'll want to see your history. The command is git log. Tools show it as a clickable timeline.

Here's a tiny simulation of what your history feels like — a list of save points with messages:

const log = [
  { hash: 'a1b2c3', msg: 'Add working homepage' },
  { hash: 'd4e5f6', msg: 'Add navigation bar' },
  { hash: '7g8h9i', msg: 'Fix mobile layout' }
];

console.log('Project history (newest last):');
log.forEach(c => console.log('  ' + c.hash + '  ' + c.msg));
console.log('\nEach hash is an ID you can return to.');

Branching to Experiment

Want to try a redesign without risking your working app? Make a branch.

  • git branch new-design — create the branch
  • git checkout new-design — switch to it

Now you're working in a parallel copy. Your main version is frozen and safe. Build wild ideas here.

Modern shortcut: git checkout -b new-design creates and switches in one step. (Your AI knows all these.)

Merging Back In

When your experiment works, you bring it into your main version with a merge.

You switch back to your main branch and merge the experiment in. If something conflicts, AI is excellent at resolving it. Here's a prompt for the whole flow:

I created a branch called `new-design`, tested it, and it works great.

Give me the exact commands to:
1. Switch back to my main branch
2. Merge `new-design` into it

If there's a merge conflict, tell me how to spot it and what to do.

Connecting to GitHub (push)

Push uploads your commits to GitHub so they're backed up online and shareable.

The easiest path: in Cursor or VS Code, click "Publish to GitHub." It creates the online repo and pushes for you.

If you prefer the terminal, your AI will give you the git remote add and git push commands. Once connected, future pushes are a single click or git push.

The .gitignore File

Some files should NOT be saved to Git — like secret API keys or huge auto-generated folders (node_modules).

A .gitignore file lists what Git should skip. This keeps your repo clean and your secrets safe.

Don't hand-write it — ask AI. A solid prompt:

Create a .gitignore file for a beginner web project.

Make sure it ignores node_modules, .env files with secrets,
and any OS junk files like .DS_Store. Explain why each
entry should be ignored, briefly.

Your Repeatable Workflow

Here's the loop you'll use every single day as a vibe coder:

  • Build a small feature with AI
  • Test it — does it work?
  • Stage and commit with a clear message
  • For risky ideas, work on a branch first
  • Push to GitHub to back everything up

Repeat. This rhythm keeps your project safe, organized, and always recoverable — no memorization required.

Quick Check

Let's check your grasp of the core Git flow.

Recap & What's Next

You can now run the full Git basics — with AI writing the commands:

  • init starts tracking a project (once)
  • stage + commit saves a snapshot with a message
  • branch lets you experiment safely, merge brings it back
  • push backs everything up on GitHub
  • .gitignore keeps secrets and junk out

Next lesson: Letting AI Write Commit Messages — get a clean, professional history with almost no effort.

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan” gratis?

Ya — teks lengkap “Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Vibe Coding, upgrade ke CoddyKit PRO. Kursus Vibe Coding mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan”?

Buat commit, cabang, dan push dengan panduan kecerdasan buatan. Kamu berlatih Vibe Coding dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Vibe Coding?

Tidak diperlukan pengalaman sebelumnya. Vibe Coding di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Vibe Coding ini?

Ya. Setiap pelajaran Vibe Coding menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Mengapa Kontrol Versi Penting
  2. Dasar-Dasar Git dengan Bantuan Kecerdasan Buatan
  3. Membiarkan Kecerdasan Buatan Menulis Pesan Commit
  4. Membatalkan Kesalahan dengan Aman
← Kembali ke Vibe Coding