Forced merges are sometimes inevitable. For instance, during a critical outage, immediate action might be necessary. However, allowing developers unrestricted access to force merge can be problematic as it may lead to frequent bypassing of essential tests (just because devs are a bit lazy sometimes 😅) Conversely, it's crucial to provide this option during emergencies, under strict policies (like requiring manual approval). An internal developer portal can be utilized to manage this. By defining a boolean property for a service, named "allow_force_merge" you can enable your git provider to conditionally allow force merges. Taking it one step further, consider implementing a self-service mechanism for requesting force merge approvals. This could involve submitting a request with a description and a TTL for the forced merge, ensuring temporary access for critical changes. Incorporating merge policies into an Internal Developer Portal offers significant advantages, primarily due to the portal's inherent understanding of service contexts. Some services span multiple repositories, and the portal's ability to manage all related repositories collectively, streamlines and enhances the management process. What is your force merge policy? 🧵