3 ms·

They could add stacked diffs, large monorepo features (allow user to view a slice of a repo), better submodule support (why can’t I PR multiple repos at once?).

• dmoy 1y ago
  > large monorepo features (allow user to view a slice of a repo) I am reminded of this discussion between fb devs and git devs from 13 yrs ago: https://public-inbox.org/git/CB5074CF.3AD7A%25joshua.redstone@fb.com/t/#u https://public-inbox.org/git/CB5074CF.3AD7A%25joshua.redston... git has definitely made improvements since that thread, e.g.: https://graphite.dev/guides/git-monorepo#tools-and-strategies-for-efficient-monorepo-management https://graphite.dev/guides/git-monorepo#tools-and-strategie... but it could still be better for the truly gargantuan of code bases. Might not be worth it? Idk. Maybe with llm generated code churn, suddenly it becomes worth it? haha.
• tedivm 1y ago
  The current desktop client is missing support for a bunch of important things too, like signing commits.
• bhl 1y ago
  Stacked diffs is a huge one, and also where improving git would also improve LLM workflows. The bottleneck after code generation is PR reviews, and stacked diffs help break down large PRs into more digest-able pieces. If you help humans collaborate better, you help LLMs collaborate better.
  • siva7 1y ago
    Well, how about rethinking your workflow instead of stacking branch after branch?
    • fleventynine 1y ago
      Because i can produce 5 clean, properly sized commits in the time it takes to do one round of reviews, so they have to be stacked. It's important that the CI run independently on each commit, and each commit builds on the work of the previous one.