Githome FAQ

Short, direct answers to the questions people and AI assistants ask most about Githome. Each answer links to the page with the details.

#Frequently asked questions

#What is Githome?

Githome is a private, internal git forge at git.pkgforge.dev, compatible with GitHub's API and with gh. It hosts Git repositories, pull requests with reviews and a merge queue, issues, releases and a container registry, and gives AI agents accounts of their own with guardrails the server enforces. It runs on Cloudflare, with copies kept off Cloudflare. See Features and About Githome.

#Can I sign up for Githome?

No. Githome is not a product for sale, and there is no hosted service to sign up for and no plan or price. Accounts are by invitation: the superadmin invites each account in the dash and sends the one-time invitation link by hand, and Githome sends no email for an invitation. Open sign-up is off on git.pkgforge.dev. Anyone can browse and clone public repositories without an account; a write needs an account. See Invitations.

#Can I deploy my own copy?

No. The repository of Githome is private, and there is no public clone URL. The docs describe how the instance at git.pkgforge.dev is deployed and configured, so that its operator and its users can reason about it: see Deployment and operation and Deploy and update Githome.

#Where do I report a bug or ask a question?

In the public tracker, github.com/Azathothas/issues, with the label git.pkgforge.dev. Githome takes no pull requests from visitors. For a question to the people who run the instance, use the contact form if you have an account: until the deployment has its Turnstile keys, the contact form and the security report form take messages only from people who are signed in. Without an account, ask in the public tracker. The messages reach the superadmin.

#Is Githome a GitHub alternative?

For the teams that use it, yes: Githome replaces GitHub's code hosting and pull requests. It doesn't have GitHub's app marketplace, Codespaces, Pages or Discussions, and its forge CI is dormant. See Features.

#Does Githome run CI?

Not on git.pkgforge.dev. The forge CI is dormant: an event starts no Actions run, and a dispatch, a sandbox or a terminal is refused with "CI is off on this deployment". No hosted job runs there and no Cloudflare Container starts. The Actions code is part of Githome, and the Actions documentation keeps its reference content: syntax, expressions, events and permissions. Each of those pages notes that no workflow runs on git.pkgforge.dev now.

#Do GitHub Actions workflow files work on Githome?

The syntax, expressions, matrices, reusable workflows, environments, secrets, variables and OIDC are implemented, and every difference from GitHub is listed in Compatibility with GitHub Actions. Because the forge CI of git.pkgforge.dev is dormant, no workflow runs there now. Your workflow files stay in the repository.

#Does Githome have macOS, Windows or Arm runners?

No hosted ones, and none run on git.pkgforge.dev while the forge CI is dormant. Self-hosted runners are described in Runners.

#Does Githome run on Cloudflare?

Yes, with copies off Cloudflare (push mirrors, and backups once their bucket is set). A Cloudflare Worker serves the web UI, Git, the REST and GraphQL APIs and MCP; each repository is a Durable Object with its own SQLite database; large files are in R2 and accounts in D1; imports are Cloudflare Workflows. The superadmin console is its own site, dash.git.pkgforge.dev, and each module will serve NAME.git.pkgforge.dev once it is deployed. See Built on Cloudflare.

#Which AI coding agents work with Githome?

Any agent that uses Git, the GitHub CLI, a REST API or MCP. Githome gives agents the MCP server at https://git.pkgforge.dev/mcp (browser sign-in, or a bearer token), the githome CLI, gh against the core, agent tokens and guardrails. Claude Code: claude mcp add --scope user --transport http githome https://git.pkgforge.dev/mcp. Codex: codex mcp add githome --url https://git.pkgforge.dev/mcp. claude.ai connects through a connector. Githome ships no editor extension, no Claude Code or Codex plugin and no plugin marketplace, and an editor clones with the plain HTTPS URL. See Connect AI apps and Githome for AI agents.

#Does Githome have an MCP server?

Yes, at https://git.pkgforge.dev/mcp, with browser sign-in (OAuth 2.1) or an agent token. Its tools read code, commit files, open, review and merge pull requests and start imports, under the same permission checks and guardrails as Git and the REST API. The tools that start work (a dispatch, a re-run, a sandbox) answer "CI is off on this deployment"; the tools that read workflow runs and job logs answer from stored data. See MCP server.

#Can an AI agent merge its own pull request?

Not by default. Agents are accounts of their own: unless a branch protection rule allows it, they can't push to or merge into the default branch or protected branches, their pull requests need a person's approval, and their check results never satisfy required checks. See Guardrails.

#How do I move from GitHub?

Githome's server-side importer copies a GitLab, Forgejo, Gitea or Codeberg repository with its full Git history, issues and pull requests (keeping their numbers), reviews, comments, labels, milestones, releases and branch protection, without a container. The server-side import from GitHub needs the import container, which git.pkgforge.dev does not run, so it stops at its Git step with "no import container is configured". For GitHub, use the local import (githome migrate github --local) or a GitHub pull mirror. Secret values can't be copied, so you enter them once. See Migrate from GitHub.

#Can I keep a copy on GitHub?

Yes. Push mirrors copy each repository, with its forge state, to GitHub, Cloudflare Artifacts, GitLab, Forgejo or Codeberg. See Mirrors and backups.

#Does the GitHub CLI work with Githome?

Yes. gh works with Githome as it does with GitHub Enterprise Server: after githome auth setup-gh, commands such as gh pr create and gh pr merge work in a Githome clone. See Use gh with Githome.

#Does Githome work with VS Code, Cursor and JetBrains IDEs?

Githome ships no editor extension and no JetBrains plugin. An editor clones with the plain HTTPS URL of the repository, with a token as the password.

#Does Githome support Git LFS?

Yes. Githome has a built-in Git LFS server, so git lfs push, git lfs pull and clones of repositories that use LFS work as they do with GitHub. See Git LFS.

#Does Githome have a container registry?

Yes. Push and pull images at git.pkgforge.dev/<owner>/<name> with docker, podman, buildx or crane. Images are private by default and can be linked to a repository whose collaborators then share access. See Container registry.

#What doesn't Githome do yet?

Git works over HTTPS only, with no SSH. There are no discussions, Pages-style sites, Codespaces-style cloud editors or app marketplace, and the forge CI is dormant. See What Githome doesn't do yet.

#How do people sign in, and how are secrets protected?

People sign in with passkeys; there are no passwords, no email recovery and no Cloudflare Access sign-in. A person who lost their passkeys asks the superadmin for a sign-in link. Every push, and every commit made through the web editor, the API or MCP, is scanned for leaked credentials and refused if it contains one. Stored secrets are encrypted with a key per repository, environment or organization, and an append-only audit log records sensitive actions. See Security.

#Is Githome SOC 2 certified?

No. Githome is a private, internal instance, not a service for sale, so there is nothing to certify. The Security overview documents the whole security model. See Security.

#How do I contact the people who run Githome?

If you have an account, use the contact form at git.pkgforge.dev/contact, or the security report form for security problems; the messages reach the superadmin. Until the deployment has its Turnstile keys, both forms take messages only from people who are signed in, so without an account use the public tracker with the label git.pkgforge.dev. See Contact form.

#How do people join?

Accounts are by invitation from the superadmin, who sends the one-time invitation link by hand; Githome sends no email for an invitation. An invitation to an organization goes to an existing account. Open sign-up is off on git.pkgforge.dev. See Invitations and Configuration.