Every question about your code deserves a place next to the code — not a pull request, not a backlog, not a Discord scroll. Point at any file or line range and start the thread right there. Each repo gets one official room, with a README badge that brings visitors in.
Rooms live now
m1ndRust · 2 members · activity startingomx-codex-app-bridgeShell · 1 members · activity startingkognit1v-intelligence-systemsPython · 1 members · activity startingSelect a file and line range, then start the thread right there.
Help, releases, ideas, and support stay scoped to the project.
Put the official doorway where GitHub visitors already arrive.
export async function loadRepo(owner, repo) { const tree = await getTree(owner, repo);Discord has your community. GitHub has your code. Neither has the conversation on your code.
The repo stays the source of truth. GitRooms adds the layer GitHub is missing: comment on exact files and line ranges, keep the answer attached to the code, and let README traffic find it.
Comment on exact files and line ranges without turning every question into a pull request.
See a live Code RoomClaim the repo once so the public conversation has one official place.
Help, ideas, releases, showcase, and support stay scoped to the project.
The room starts around the code. The badge puts its official doorway where developers already decide whether to join: the README.
The badge only represents an official GitRooms room.
Use markdown for README.md or HTML for docs and sites.
The badge opens the room scoped to that exact repo.
README.md
Official room badge
return tree.filter((file) => file.type === "blob" && file.path );} A code thread starts on a specific file and line range.
Every reply stays attached to that code, so the answer is easy to find later.
Put the door in the README so people arrive from GitHub with context.
Find rooms by repo, profile, language, project name, or current activity.
[](https://gitrooms.com/github/OWNER/REPO)