{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib2my4nmrez37gncrmmlf3qixzvis3i2wohstb7iopq3jtzbvwbv4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlbw2juos3z2"
  },
  "path": "/t/feature-idea-direct-github-connection-from-chatgpt/1380428#post_3",
  "publishedAt": "2026-05-07T17:49:53.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@fruitlady"
  ],
  "textContent": "Hi @fruitlady, this is basically the current “last mile” gap in the GitHub integration.\n\nRight now ChatGPT’s GitHub connector is mostly read-focused, so repo analysis/search works well, but direct commits, PRs, and deploy flows still aren’t native in normal chat UX.\n\nWhich makes the friction pretty obvious:\n\n`chat -> copy files -> git push -> deploy`\n\n…instead of the workflow people actually want:\n\n`chat -> git push -> auto deploy`\n\nThe infrastructure already exists through GitHub APIs, Vercel auto-deploys, MCP tooling, IDE agents, etc. The harder part is mostly around permissions, approvals, rollback handling, and org-level safety controls.\n\nA lot of folks are asking for exactly what you described, and we’re forwarding this feature request to the team for logging since this workflow gap keeps coming up in developer feedback.\n\n-Mark G.",
  "title": "Feature Idea: Direct GitHub Connection from ChatGPT"
}