You won't face any terrible consequence, just the history will look kind of confusing.

You could change the commit message by doing

git commit --amend git push --force-with-lease # (as opposed to --force, it doesn't overwrite others' work) 

BUT this will override the remote history with yours, meaning that if anybody pulled that repo in the meanwhile, this person is going to be very mad at you...

Just do it if you are the only person accessing the repo.

You won't face any terrible consequence, just the history will look kind of confusing.

You could change the commit message by doing

git commit --amend git push --force-with-lease # (as opposed to --force, it doesn't overwrite others' work) 

BUT this will override the remote history with yours, meaning that if anybody pulled that repo in the meanwhile, this person is going to be very mad at you...

Just do it if you are the only person accessing the repo.

You won't face any terrible consequence, just the history will look kind of confusing.

You could change the commit message by doing

git commit --amend git push -f 

BUT this will override the remote history with yours, meaning that if anybody pulled that repo in the meanwhile, this person is going to be very mad at you...

Just do it if you are the only person accessing the repo.

You won't face any terrible consequence, just the history will look kind of confusing.

You could change the commit message by doing

git commit --amend git push --force-with-lease # (as opposed to --force, it doesn't overwrite others' work) 

BUT this will override the remote history with yours, meaning that if anybody pulled that repo in the meanwhile, this person is going to be very mad at you...

Just do it if you are the only person accessing the repo.