True or False. It is recommended to run git commit --amend after you've pushed your changes to the remote.

True or False. It is recommended to run git commit --amend after you've pushed your changes to the remote.

• A. True
• B. False
• C. Only if you have a clean history
• D. Depends on your workflow

Answer: (B)

Modifying history after it has been shared is risky. git commit --amend changes the content of the most recent commit and rewrites its hash. If that commit has already been pushed to the remote, amending locally will create a mismatch between your local history and the remote history. To reconcile them, you’d have to force-push, which can overwrite the remote history and disrupt collaborators’ work. That’s why, in practice, you typically avoid using amend after pushing. Instead, add a new commit that fixes what’s needed, or, if the history must be rewritten on a branch others are using, coordinate with the team and consider safer options like revert.

Modifying history after it has been shared is risky. git commit --amend changes the content of the most recent commit and rewrites its hash. If that commit has already been pushed to the remote, amending locally will create a mismatch between your local history and the remote history. To reconcile them, you’d have to force-push, which can overwrite the remote history and disrupt collaborators’ work. That’s why, in practice, you typically avoid using amend after pushing. Instead, add a new commit that fixes what’s needed, or, if the history must be rewritten on a branch others are using, coordinate with the team and consider safer options like revert.