Commit force pushed

Data Loss: Force pushes can overwrite changes made by other team members, leading to data loss and making it difficult to track who made what changes.

Reduced Accountability: Force pushes can make it difficult to track who made what changes to the codebase, reducing accountability and transparency.

Security Risks: Force pushes can introduce security vulnerabilities into the codebase, allowing attackers to exploit the organization’s systems or access sensitive data, leading to data breaches, financial losses, or reputational damage.

Operational Disruptions: Force pushes may cause unexpected errors, crashes, or downtime in the organization’s systems, disrupting business operations and causing financial losses.

Delayed Detection of Issues: Force pushes can bypass proper review and testing processes, allowing issues such as bugs or performance problems to go unnoticed until they cause significant problems in production.