ตัวอย่างบทเรียน

Installation and Setup: Getting Git Ready for First Use

Install Git on Windows, macOS, and Linux, and explore why configuring your name and email isn't just a formality but an integral part of commit history. Set up a user-friendly terminal and several useful aliases to work comfortably from day one, rather than struggling with lengthy commands.

Git installation git config global configuration

คุณจะเรียนรู้อะไรในบทเรียนนี้

You will be able to install Git on any operating system and verify the installation was successful.
You will understand why Git requires a name and email, and how this information appears in commit history.
You will be able to configure global settings in a way that won't require future adjustments.

จุดเริ่มต้นของบทเรียน

Why Git Bash is the Best Choice for Windows

Git Bash provides a full Unix environment for Windows
Solves line ending differences between Windows and Unix systems
Ensures command consistency with Linux/Mac
Prevents collaboration errors

If you're working on Windows, the standard command prompt can cause unexpected issues when using Git, particularly with line ending characters and file paths. Git Bash solves these problems by providing a complete Unix environment right in Windows. This means all commands will work the same as they do for your colleagues on Linux or Mac. You'll avoid numerous collaboration errors and save hours of debugging time. This is especially important for new developers who are just learning version control systems.

Step by Step: Downloading and Installing Git

Open git-scm.com in your browser
Download the latest version of Git for Windows
Run the installer as administrator
Accept the license agreement

Open your browser and navigate to the official website git-scm.com. On the homepage, you'll immediately see a prominent download button that automatically detects your operating system. Download the installer and run it as administrator. The first screen will present you with the license agreement—scroll through and click 'Next'. I recommend keeping all default settings unless you're confident about making changes.

Critical Git Installation Settings

Select 'Use Git from Windows Command Prompt'
Set 'Checkout as-is, commit Unix-style'
Keep Nano as the default editor for beginners
These settings are crucial for compatibility

One of the key moments during installation is selecting the right options. When configuring PATH, choose 'Use Git from the Windows Command Prompt'. This will allow you to run Git from any command line. Next, for line ending conversion, select 'Checkout as-is, commit Unix-style line endings' — this ensures compatibility with other systems. Keep Nano as the default editor if you're not familiar with alternatives — it's simpler for beginners. These settings are absolutely crucial for Git to function correctly in the future.

บทเรียนฉบับเต็มใช้ได้เมื่อสมัครสมาชิก

ฉบับเต็มมีสไลด์เพิ่มอีก 29 สไลด์

วิดีโอ สไลด์ทั้งหมด โน้ต แบบทดสอบ AI ติวเตอร์ และการสัมภาษณ์จะเปิดหลังเข้าสู่ระบบและสมัครสมาชิก

เข้าสู่ระบบหรือลงทะเบียน สมัครสมาชิก

เนื้อหาบทเรียน

Why Git Bash is the Best Choice for Windows
Step by Step: Downloading and Installing Git
Critical Git Installation Settings
Verifying Git Installation
Installing Git on macOS: The Easy Way with Homebrew
Installing Git on Linux: Commands for Different Distributions
How to Verify Git is Installed Correctly
Your Digital Signature in Git
Setting Up Your Name and Email for Commits
Consequences of Incorrect Author Configuration
Git Global Settings: Your Digital Fingerprint
Practice: Configuring Developer Name and Email
Verifying Git Configuration
Three Levels of Git Configuration: System, Global, Local
System Settings: General Rules for All
Global Settings: Your Personal Profile
Local Settings: Project-Specific Rules
Why Does Git Need a Text Editor?
Setting Up Your Preferred Editor for Git
Example Commands for Popular Editors
Git Aliases: Your Personal Command Dictionary
Creating Your First Alias: git status
Alias for Beautiful History Visualisation
How to View All Created Aliases
Colour Output in Git: More Than Just Pretty Colours
Enabling Colour Output in Git
Customising Colours to Your Preferences
Common Author Configuration Mistakes
Global vs Local Settings: Which Takes Precedence?
Editor Won't Launch? Troubleshooting Guide
30-Second Settings Verification
Your Git is Ready to Go!