Nge-GIT (Belajar Git Bareng)
5 likes771 views
This document provides an introduction to Git and common Git workflows. It discusses what Git is, how it stores data as snapshots rather than file changes, and its advantages as a distributed version control system where the full code history is stored locally. It then demonstrates basic Git commands like init, add, commit, status, branch, merge, tag and working with remotes. Key points covered include initializing and cloning repositories, tracking changes, committing work, branching and merging, and sharing code via remote repositories.
![$ git commit
[master e0b06a1] mencoba commit
1 file changed, 4 insertions(+)](https://image.slidesharecdn.com/nge-git-151221141007/85/Nge-GIT-Belajar-Git-Bareng-70-320.jpg)
Nge-GIT (Belajar Git Bareng)
- 2. Perkenalkan
- 3. Mizan General Manager T’Lab http://tlab.co.id Pengguna Git Ilkomp 2006
- 4. Semacam apa Git ?
- 5. Git Open source distributed version control system designed for speed & efficiency
- 6. Apa pula Version Control?
- 7. ● Sistem untuk mencatat perubahan data ● Memungkinkan pengembangan secara bersama ● Tahu siapa yang merubah dan kapan data dirubah ● Memungkinkan mengembalikan data seperti semula Version Control
- 8. Git mercurial (hg) bazaar subversion (svn) concurrent version system (cvs) perforce visual source safe Contoh Version Control
- 9. Apa maksud distributed version control ?
- 10. (Hampir) semua data berada di lokal
- 11. Keuntungan Data di Lokal ● Ada backup ● Bekerja jadi lebih cepat ● Bekerja offline (tanpa koneksi internet)
- 12. Apa yang bisa dilakukan tanpa Internet ● Performing a diff ● Viewing file history ● Committing change ● Merging branches ● Obtaining other revisions of a ifle ● Switching branches
- 13. Maksud “designed for speed & efficiency” ?
- 14. Data (hampir) tidak dihapus Data di-Snapshots
- 15. Perbedaan Patch & Snapshots Storing data as changes to a base version of each file Storing data as snapshots of the project over time
- 31. Basic Git
- 32. Langkah awal
- 33. $ git config --global user.name “Mizan” $ git config --global user.email “baobaz@gmail.com”
- 34. Getting a Repo
- 35. Membuat Repo
- 36. Git init
- 37. $ touch README.md $ git init
- 38. $ tree -a . ├── .git │ ├── branches │ ├── config │ ├── description │ ├── HEAD │ ├── hooks │ │ ├── applypatch-msg.sample │ │ ├── commit-msg.sample │ │ ├── post-update.sample │ │ ├── pre-applypatch.sample │ │ ├── pre-commit.sample │ │ ├── prepare-commit-msg.sample │ │ ├── pre-push.sample │ │ ├── pre-rebase.sample │ │ └── update.sample │ ├── info │ │ └── exclude │ ├── objects │ │ ├── info │ │ └── pack │ └── refs │ ├── heads │ └── tags └── README.md 10 directories, 14 files
- 39. $ tree -a . ├── .git │ ├── branches │ ├── config │ ├── description │ ├── HEAD │ ├── hooks │ │ ├── applypatch-msg.sample │ │ ├── commit-msg.sample │ │ ├── post-update.sample │ │ ├── pre-applypatch.sample │ │ ├── pre-commit.sample │ │ ├── prepare-commit-msg.sample │ │ ├── pre-push.sample │ │ ├── pre-rebase.sample │ │ └── update.sample │ ├── info │ │ └── exclude │ ├── objects │ │ ├── info │ │ └── pack │ └── refs │ ├── heads │ └── tags └── README.md 10 directories, 14 files
- 40. $ touch README.md $ git init $ git add .
- 41. tree -a . ├── .git │ ├── branches │ ├── config │ ├── description │ ├── HEAD │ ├── hooks │ │ ├── applypatch-msg.sample │ │ ├── commit-msg.sample │ │ ├── post-update.sample │ │ ├── pre-applypatch.sample │ │ ├── pre-commit.sample │ │ ├── prepare-commit-msg.sample │ │ ├── pre-push.sample │ │ ├── pre-rebase.sample │ │ └── update.sample │ ├── index │ ├── info │ │ └── exclude │ ├── objects │ │ ├── e6 │ │ │ └── 9de29bb2d1d6434b8b29ae775ad8c2e48c5391 │ │ ├── info │ │ └── pack │ └── refs │ ├── heads │ └── tags └── README.md 11 directories, 16 files
- 42. $ touch README.md $ git init $ git add . $ git commit -m ‘first commit’
- 43. tree -a . ├── .git │ ├── branches │ ├── COMMIT_EDITMSG │ ├── config │ ├── description │ ├── HEAD │ ├── hooks │ │ ├── applypatch-msg.sample │ │ ├── commit-msg.sample │ │ ├── post-update.sample │ │ ├── pre-applypatch.sample │ │ ├── pre-commit.sample │ │ ├── prepare-commit-msg.sample │ │ ├── pre-push.sample │ │ ├── pre-rebase.sample │ │ └── update.sample │ ├── index │ ├── info / exclude │ ├── logs │ │ ├── HEAD │ │ └── refs / heads / master │ ├── objects │ │ ├── e6 / 9de29bb2d1d6434b8b29ae775ad8c2e48c5391 │ │ ├── f9 / 3e3a1a1525fb5b91020da86e44810c87a2d7bc │ │ ├── ff / 0952b14f24609b47d910df46ee944650f60054 │ │ ├── info │ │ └── pack │ └── refs │ ├── heads / master │ └── tags └── README.md 16 directories, 22 files
- 45. Git Clone
- 46. $ git clone git@github.com:laravel/laravel.git Atau $ git clone https://github.com/laravel/laravel.git
- 47. $ git clone https://github.com/laravel/laravel.git Cloning into 'laravel'... remote: Counting objects: 25800, done. remote: Compressing objects: 100% (41/41), done. remote: Total 25800 (delta 23), reused 0 (delta 0), pack-reused 25759 Receiving objects: 100% (25800/25800), 9.69 MiB | 116.00 KiB/s, done. Resolving deltas: 100% (12922/12922), done. Checking connectivity... done. $ cd laravel $ ls app composer.json gulpfile.js phpunit.xml resources tests artisan config package.json public server.php bootstrap database phpspec.yml readme.md storage
- 48. A Basic Workflow
- 49. A Basic Workflow ● Edit files ● Stage the changes ● Review your changes ● Commit the changes
- 54. A Basic Workflow ● Edit files ● Stage the changes ● Review your changes ● Commit the changes
- 55. $ vim README.md # My First Git Senangnya bisa menggunakan git
- 56. $ git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in.. modified: README.md no changes added to commit (use "git add" and/or "git com..
- 57. A Basic Workflow ● Edit files ● Stage the changes ● Review your changes ● Commit the changes
- 58. Git Add
- 61. $ git add . $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: README.md
- 62. $ git add . $ git status On branch master Changes THAT ARE STAGED: (use "git reset HEAD <file>..." to unstage) modified: README.md
- 63. stage file setelah melakukan perubahan
- 64. stage file setelah melakukan perubahan
- 65. A Basic Workflow ● Edit files ● Stage the changes ● Review your changes ● Commit the changes
- 66. Git commit
- 69. $ git commit mencoba commit # Please enter the commit message for your changes. Lines .. # with '#' will be ignored, and an empty message aborts .. # On branch master # Changes to be committed: # modified: README.md
- 70. $ git commit [master e0b06a1] mencoba commit 1 file changed, 4 insertions(+)
- 71. A Basic Workflow ● Edit files vim / emacs / etc ● Stage the changes git add (file) ● Review your changes git status ● Commit the changes git commit
- 72. A Basicer Workflow ● Edit files vim / emacs / etc ● Stage & Commit git commit -a
- 74. Another Basic Git ● Ignoring Files ● Removing Files ● Moving Files
- 76. $ touch .gitignore $ vim .gitignore .env $ touch .env $ git status On branch master Untracked files: (use "git add <file>..." to include in what will be.. .gitignore nothing added to commit but untracked files present.. $ git add . $ git commit -m ‘add gitignore’
- 77. Removing Files git rm <file>
- 78. $ git rm README.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: README.md
- 79. Moving Files git mv <file>
- 80. $ git mv README.md README $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README
- 81. Undo
- 82. Undo Commit git commit --amend
- 83. Unstaging a Staged File git reset HEAD <file>
- 84. Unmodifiying a Modified File git checkout -- <file>
- 85. Branching
- 86. git branch & git checkout
- 103. Git Merge
- 113. ● clone the code that is in production ● create a branch for issue #53 (iss53) ● work for 10 minutes ● someone ask for a hotfix for issue #102 ● checkout ‘production’ ● create a branch (iss102) ● fix the issue ● checkout ‘production’ merge ‘iss102’ ● push ‘production’ ● checkout ‘iss53’ and keep working
- 125. Distributed Workflow fetch, pull, & push
- 126. pull = fetch + merge
- 127. a Who in the what now?
- 135. Multiple Remotes
- 160. Popular Workflows
- 169. Dictator and Lieutenants Model
- 188. Remotes Are Branches
- 205. Working with Remotes
- 206. Showing Your Remotes git remote git remote -v
- 207. Adding Remote Repositories git remote add <remote-name> <URL>
- 208. Fetching & Pulling from Remotes git remote <remote-name>
- 209. Pushing to Your Remotes git push <remote> <branch>
- 210. Inspecting a Remote git remote show <remote-name>
- 211. Renaming & Remove Remotes git remote rename <remote-name> <remote-newname> git remote rm <remote-name>
- 212. Tagging
- 213. Listing Your Tags git tag
- 214. Creating Tags Lightweight tag Annotated tags (pointer) (store as full object)
- 215. Annotated Tags git tag -a <tagname>
- 216. Listing Lightweight Tags git tag <tagname>
- 217. Tagging Later git tag -a <tagname> <commit>
- 218. Sharing Tags git push <remote> <tagname>
- 219. Checking out Tags git checkout -b <branchname> <tagname>
- 220. Thank you for watching any question?