Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8495097
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T23:28:33+00:00 2026-06-10T23:28:33+00:00

Suppose you do a Git commit and then push to a remote repo. Then

  • 0

Suppose you do a Git commit and then push to a remote repo. Then someone else pulls. Then you make a change and amend the commit.

When the amended commit is pushed and then pulled by someone else, will it cause a problem?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T23:28:34+00:00Added an answer on June 10, 2026 at 11:28 pm

    Yes; amending a commit creates an entirely new commit with a completely different SHA1 hash value (ID). The rule of thumb is that you should never rebase or amend commits that have been pushed to a shared branch.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Suppose I have Git repository like this: git-repo/ directory_1/ directory_2/ directory_3/ This has a
I'm trying to push my git repo to a heroku servers, now I used
Suppose I have the following git commits: aaaaaa bbbbbb cccccc (the latest) I would
Suppose I have a git repository with several branches. I suspect some of the
Suppose I have a git repos that contains original.script . At some point, I
Suppose I was on master branch and created a new branch: git checkout -b
I often face this problem with git: I clone a git repo of some
For example, I create file a in the repo(suppose I'm on the master branch),
Suppose I have this folder structure: /projectroot/foo/bar/subfoo/foo.txt Now I change something in foo.txt a
I had made some changes to a file under a git repo, I committed

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.