After all, everyone has done a lot of work on the original basis, so the forced update of their local libraries will not be displayed. The only thing you can do is to tell everyone else after you force the update and let themfetch之后rebasego to the latest submission. There must be conflicts that need to be resolved. Just don't add the deleted information back.
You ask other colleagues to pull down the code from the remote warehouse and merge it locally when pushing code to the server. That means switching to the master branch first,
Normally speaking, this situation will not happen. Because you have also modified the remote end, the version on your colleagues has fallen behind. They have to pull down the latest code from the remote end before pushing it. Is it possible? Are they also forced to recommend it like you?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There is no obvious solution
After all, everyone has done a lot of work on the original basis, so the forced update of their local libraries will not be displayed.
The only thing you can do is to tell everyone else after you force the update and let them
fetch之后rebasego to the latest submission. There must be conflicts that need to be resolved. Just don't add the deleted information back.You ask other colleagues to pull down the code from the remote warehouse and merge it locally when pushing code to the server. That means switching to the master branch first,
Then, switch to your own branch
Finally, pushing
Normally speaking, this situation will not happen. Because you have also modified the remote end, the version on your colleagues has fallen behind. They have to pull down the latest code from the remote end before pushing it. Is it possible? Are they also forced to recommend it like you?