Git: command 'github.codespaces.publish' not found

[thecherrie]

Opening this to draw more attention to this issue, shown here (https://github.com/orgs/community/discussions/67031)

---

I'm trying to publish my codespaces branch to a private repository, but after clicking publish branch, the following error is shown:

Git: command 'github.codespaces.publish' not found

I can't seem to find anything on the internet on this, so I am making this.

The template I used for this codespace was (https://github.com/theodorusclarence/ts-nextjs-tailwind-starter)

Any ideas? Thank you

[dmgardiner25]

@thecherrie Does this consistently reproduce for you? I haven't had any luck hitting this myself. Can I have you export your logs (F1 > Codespaces: Export Logs) and email them to me at dmgardiner25@github.com to help me look into this further?

[Killerking88]

Git: command 'github.codespaces.publish' not found

[redah26]

Opening this to draw more attention to this issue, shown here (https://github.com/orgs/community/discussions/67031)

---

I'm trying to publish my codespaces branch to a private repository, but after clicking publish branch, the following error is shown:

Git: command 'github.codespaces.publish' not found

I can't seem to find anything on the internet on this, so I am making this.

The template I used for this codespace was (https://github.com/theodorusclarence/ts-nextjs-tailwind-starter)

Any ideas? Thank you

[sudheerxdev]

I faced a similar issue while working in GitHub Codespaces.

From what I observed, this error usually occurs when the GitHub Codespaces extension or related VS Code commands fail to load properly inside the browser/editor environment.

A temporary workaround that worked for me was using Git directly from the terminal instead of the "Publish Branch" UI button:

git add .
git commit -m "your commit message"
git push origin <branch-name>

You can also try:

• reloading the Codespace,
• reopening the browser tab,
• or restarting the VS Code server inside Codespaces.

It may also be related to extension initialization issues in browser-based VS Code sessions.

Hope this helps someone facing the same issue.