In October 2024, Elastic experienced a significant customer outage when a change made by automation unintentionally set their most critical public repositories on GitHub to private. This incident arose from an effort by Elastic's Platform Engineering Productivity and InfoSec Product Security teams to enhance their source code supply chain security. The goal was to migrate repositories with internal visibility to private visibility on GitHub. However, a combination of factors led to the unintended consequence of affecting public-facing repositories. This event highlighted the risks of automation acting on assumptions without verifying real-world states. Elastic has learned valuable lessons from this incident, which they deem worth sharing. The author, Jamie Tanna, is a senior software engineer and open-source advocate who enjoys exploring technical issues. He recently departed Elastic but will miss his colleagues. The company reserves the right to modify or delay the release of any features mentioned.