Safe History-Rewriting Process

After a developer successfully rewrites the history on their local machine, they must update the remote repository in Azure Repos. Because the local history no longer matches the cloud version, the developer must perform a force-push to overwrite the old commits. This action can easily disrupt the work of other team members who are working on the same codebase, so it is critical to notify and coordinate with the team beforehand. Once the push is complete, the team must verify that the cloud repository successfully synchronizes and no longer contains the removed data.