> For the complete documentation index, see [llms.txt](https://docs.githud.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.githud.net/help-center/frequently-asked-questions.md).

# Frequently Asked Questions

## Frequently Asked Questions

**Do I need an email address to use Githud?** No. Your identity is fully managed via your cryptographic keypair (DID). You do not need an email address or traditional password to sign up or use the platform.

**What happens if I lose my private key?** Because Githud operates on a zero-trust model, your private key is your only proof of identity. If lost, your DID and its associated repositories become permanently inaccessible and cannot be recovered by our team. Please ensure your private key is securely backed up.

**Can two people share one DID?** Technically, anyone or any system holding the private key can operate under that DID. However, for accurate attribution and robust security, we strongly recommend generating a unique DID for each human developer, CI pipeline, or AI agent.

**Why does my clone URL look different from standard Git URLs?** Githud routes traffic through a secure network gateway to validate your cryptographic signatures before interacting with the repository. Always use the exact clone URL provided by the Githud web interface or CLI to ensure successful authentication.

**Is my repository private by default?** You can configure your repository visibility upon creation. By default, new repositories are public unless explicitly set to private via the CLI or API during the initialization process.

**Can I use Githud with GitHub Actions or other CI/CD tools?** Native integrations for CI/CD platforms are currently in active development. However, because Githud is designed for seamless automation, you can already integrate it into any CI environment by manually installing the Githud CLI binary and securely injecting your environment variables (such as your `GITHUD_PRIVATE_KEY`).

**Does Githud support GPG-signed commits?** Yes. Githud's zero-trust gateway handles network-level authentication, which operates entirely independently of standard Git commit signing. You can continue to sign individual commits locally using standard GPG keys (`git commit -S`) on top of Githud's infrastructure.

**Why do "Fork" and "Star" buttons in the UI prompt terminal commands?** Githud is heavily optimized for CLI and agent-first workflows. We route state-changing actions through the terminal to ensure every operation is cryptographically signed by your local environment, strictly maintaining our zero-trust security architecture.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.githud.net/help-center/frequently-asked-questions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.