Video: Correct a local commit message or content
The video plays in YouTube’s player, in privacy-enhanced mode.
- 5 min video
- English narration · English and Arabic captions
- Watch on YouTube
Correct a typo and message in one private hero commit while retaining its old tip. Learn why amend replaces identity and why unrelated staged content must stay out.
Read the full lesson
The article has every step and command from the video, the practice exercise and the questions.
Video transcript
The narration of the video, cue by cue.
- Start from the exact checkpoint.
- Name the branch, index and working version.
- Prepare only the isolated course copy.
- Protect the private draft before replacing it.
- Save the complete intended correction.
- Review the index, not only the message.
- Amend replaces the actual last commit.
- Write the corrected subject explicitly.
- Submit the replacement only once.
- Same parent does not mean same identity.
- Message-only editing has a separate scope.
- What does amend create?
- Git objects are immutable; replacement gets a new ID.
- What must be reviewed?
- Composer amend uses the index and last commit context.
- Parent of corrected C′?
- The replacement occupies the same ancestry position.
- Add an unrelated staged file before amend: content?
- The current index defines the replacement tree.
- Draft was published: proceed as private?
- Published identity may be used by others.
- Which evidence is required?
- Verify both replacement identity and intended content.
- Verify the actual result, not just a message.
- Predict the changed input before acting.
- Preserve useful work before recovery.
- Prove the checkpoint before continuing.
- Keep the verified result for the next step.