Copilot replied: “You’re welcome, Maya. I’ve also backported your retry logic to the release/2025.12 branch. See you tomorrow.” The November 28, 2025 updates didn’t just add features. They turned GitHub Copilot from a code completion tool into an autonomous, context-aware, safe engineering partner — one that finally understood that the best code is the code you don’t have to write.
The Wednesday That Copilot Read the Room github copilot updates november 28 2025
She didn’t review code; she reviewed pull request preview . “When did this become my junior dev?” she whispered. Next, she moved to the database migration ticket. The documentation was a mess. She typed: /memory what’s the schema for the old user_events table? Copilot replied: “You’re welcome, Maya
Copilot didn’t guess. It had been silently indexing her entire repo for the last 24 hours. It replied: Based on migrations/2024-03-12_init.sql and models/legacy/UserEvent.js , the table has columns user_id (uuid), action (varchar), and created_at (timestamp). Note: action has a typo: ‘subscrioption’. Do you want me to fix that in the new migration? Maya blinked. “Yes. And also…” she started typing, but Copilot interrupted (politely): “I see you also have a user_preferences table. The new time-series DB (QuestDB) doesn’t support JSONB. Would you like me to flatten those fields into columns?” This was the update. It had learned her team’s naming conventions, common bugs, and even her lead’s preference for explicit error handling. 3. The “Safety Catch” (Policy Enforcement) At 3 PM, Maya got reckless. She asked Copilot in plain English: Write a cron job that deletes inactive users. They turned GitHub Copilot from a code completion