返回资讯中心
外部精选
软件工程
#开发者实时流

Gitby – Stop fixing conflicts. Prevent them

No. Your repositories stay on GitHub and you keep using git. gitby connects through your GitHub account and adds file claims, notes, presence, chat, and access requests on top.

Hacker News 最新gitby2026/10/19 · 28 天前2 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

No. Your repositories stay on GitHub and you keep using git. gitby connects through your GitHub account and adds file claims, notes, presence, chat, and access requests on top.

gitby never stores your code. Pushes made through gitby pass through its push service on the way to GitHub, and the dashboard's diff view fetches changes from GitHub for your browser; neither keeps a copy. What gitby stores is coordination data: paths, claims, requests, notes, team membership, and activity. No file contents, diffs, note text, or chat text ever enter its statistics.

It changes the file permissions your operating system already enforces, so the rule works in any editor. A file someone else holds is read-only for you. By default every file you have not claimed is read-only too; a repository can instead be set to claim on edit, where files stay writable and a file is claimed as you edit it.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →