From 97dbdfb9c8181d91f5eb0c3bd7603e717041aa98 Mon Sep 17 00:00:00 2001 From: Cal Corum Date: Fri, 13 Feb 2026 15:09:00 -0600 Subject: [PATCH] store: Check for production hotfixes before deploying --- ...or-production-hotfixes-before-deploying-9d18fe.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 graph/insights/check-for-production-hotfixes-before-deploying-9d18fe.md diff --git a/graph/insights/check-for-production-hotfixes-before-deploying-9d18fe.md b/graph/insights/check-for-production-hotfixes-before-deploying-9d18fe.md new file mode 100644 index 00000000000..54abfc16326 --- /dev/null +++ b/graph/insights/check-for-production-hotfixes-before-deploying-9d18fe.md @@ -0,0 +1,12 @@ +--- +id: 9d18fe1c-ec20-4c6b-ac66-f0a646da329d +type: insight +title: "Check for production hotfixes before deploying" +tags: [ai-assistant, deployment, git, workflow] +importance: 0.5 +confidence: 0.8 +created: "2026-02-13T21:09:00.334298+00:00" +updated: "2026-02-13T21:09:00.334298+00:00" +--- + +Production servers may have local commits (hotfixes) not pushed to the remote repo. Before deploying, check git log on production vs origin to detect divergence. Found this when ai-pm had a config.py logger import fix that wasn't in Gitea. Use git pull --rebase to cleanly stack changes. Also check for unstaged changes (git stash first if needed).