Submissions that have been uploaded to the server, whether reset or rebase, will be rejected by teammates;
Excessive submissions will only record the changes. If they are all positive modifications, they will not increase the size, but are the recommended best practice strategies;
When you have permission to reset the server, you just force your local and server to jump to the corresponding submission; your teammates are still at the original position, and the result of them updating and submitting again will be very dramatic;
Rebase is good for your local and server in this case; your teammates will scold you and create a new branch for me, which is not beautiful at all. At the same time, the redundancy of local submissions has really increased. ..
Yes, you can find it just by searching
But I really don’t recommend doing this.
@AlexChen has already said to do it through the reset command:
The effect of this command is to undo all commits after this commit. You can also do it through the revert command:
The effect is to cancel a certain submission.
This is indeed very risky, so be careful.
In my impression, the rebase command can merge redundant commits
http://www.ruanyifeng.com/blog/2015/08/git-use-process.html
Refer to this article
means
git commit
just save file changes, so it won’t take up much space