git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Suggestion: Real-time or Conflict-Reducing Collaboration Support for Specific Directories

From
胡胡锦 <hujin2@sunline.cn>
Date
May 28, 2026, 05:15 UTC
Message-ID
<tencent_530FD5EC0E2FA9A005AB4725@qq.com>
Dear Git Team,
My name is Hujin, and I am an IT engineer from China. I have been using Git for more than 10 years.
First of all, I would like to express my appreciation for Git. In my experience, Git remains one of the best and most reliable version control systems in modern software development. It has played an important role in many projects I have worked on.
However, I have also encountered a recurring difficulty in daily use. For certain types of files, especially files under script directories or other frequently modified directories, conflicts happen quite often because updates are not synchronized in real time. In some project scenarios, multiple engineers may edit related scripts at the same time, and this can lead to repeated merge conflicts and extra coordination costs.
I wonder whether Git could provide, in future versions, some optional features similar to online collaborative documents, or directory-level collaboration mechanisms for specific files or folders. For example, users could enable special real-time update, lock, notification, or conflict-reduction behavior for selected directories such as scripts. This could help reduce conflicts and make Git even more convenient for teams working on highly shared files.
I understand that Git is designed as a distributed version control system, and such functionality may not be simple to implement. Still, I believe an optional feature in this direction could be very helpful for many engineering teams.
Thank you for your great work on Git. I look forward to hearing your thoughts.
Best regards,Hujin
Next: Christian Couder
Message 1 of 2 in “Suggestion: Real-time or Conflict-Reducing Collaboration Support for Specific Directories”
  1. 胡锦May 28, 2026
  2. Christian CouderMay 28, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.