- Git amend is used to change the last commit message/information
- Once run the commit an editor opens, edit the information/message, save it
- Git ammend only changes the commit message of previous last commit only
- It won’t change anything
1. Introduction
2. Git Basics
3. Git Terminology
- 3.1 - Source Code Management
- 3.2 - Version Control System
- 3.3 - Centralised Version Control System vs Distributed Version Control System
- 3.4 - What is Repository & Types ?
- 3.5 - What is Git bare repository ?
- 3.6 - Working Directory
- 3.7 - Staging Area
- 3.8 - Git local Repository
- 3.9 - Git Head, Git Log and Git Reflog
4. Git Branching
5. Git - Github
6. Git Add (Git staging)
7. Git Commit
-
7.1 - Git Commit
(Creating Commit) -
7.2 - Git Log
(See Commit List/History) -
7.3 - Git Show
(See Commit Information) -
7.4 - Git Ammend
(Renaming Last Commit) -
7.5 - Git rebase reword
(Renaming Old Commits) -
7.6 - Git bisect
(Markig commits good/bad) -
7.7 - Git Merge branch
(Copying Commits) -
7.8 - Git Merge commit
(Copying Commits fast forword) -
7.9 - Git Merge Rebase
(Copying Commits as Latest) -
7.10 - Git reset
(Move/Rollback to old commit) -
7.11 - Git revert
(Revert the file changes with new commit) -
7.12 - Git rebase drop
(dropping commit from history) -
7.13 - Git rebase squash
(Merging commit to it's next commit) -
7.14 - Git cherrypick
(copying commit chanes from one branch to another)