<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github-Copilot on Kuldeep Pisda</title><link>https://kdpisda.in/tag/github-copilot/</link><description>Recent content in Github-Copilot on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/github-copilot/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Copilot Moves Into Slack, and Governance Becomes the Interesting Part</title><link>https://kdpisda.in/github-copilot-agent-slack-code-channels/</link><pubDate>Sat, 22 Aug 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/github-copilot-agent-slack-code-channels/</guid><description>&lt;p&gt;Yesterday GitHub shipped something that looks, on the surface, like a chat integration: you can now mention &lt;code&gt;@GitHub&lt;/code&gt; in a Slack conversation and have the Copilot coding agent triage a bug, investigate a failure, and open a pull request, all without leaving the thread where your team was already talking. That is a nice convenience. The part worth an engineer&amp;rsquo;s attention is underneath it, GitHub is quietly asking every organization to decide, explicitly, how much autonomy an agent gets before a human has to sign off.&lt;/p&gt;</description></item></channel></rss>