But you had to do a git pull --rebase which, it would seem, wiped out the original commit, probably because it's now empty. If you'd done just git pull, without the rebase, you'd have a conflict.
All this rewriting of history after it's been pushed to a public remote repo seems pretty messy.
no bro, if you do pull --no-rebase it's same, no conflicts are there because opencommit doesn't change any code, only message. SHA becomes different, but git doesnt create any conflicts you would need to solve, because code is same.. all good :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But you had to do a
git pull --rebasewhich, it would seem, wiped out the original commit, probably because it's now empty. If you'd done justgit pull, without the rebase, you'd have a conflict.All this rewriting of history after it's been pushed to a public remote repo seems pretty messy.
no bro, if you do
pull --no-rebaseit's same, no conflicts are there because opencommit doesn't change any code, only message. SHA becomes different, but git doesnt create any conflicts you would need to solve, because code is same.. all good :)