-
## Context
Stacked diffs are extremely nice for productivity, can read more
1. https://graphite.dev/guides/stacked-diffs
2. https://graphite.dev/guides/phabricator-source-code-management-tool
b…
-
Problem:
Some users find that reformatting entire files introduces unwanted changes to their commits, due to formatter behavior changing over time, or just because they're working on code that wasn…
-
Teammates told me they can't check out my unapproved stacked diffs. Say I have stacked diffs: diff1 -> diff2 -> diff3 -> diff4, and none of them are approved yet. What's the best way someone can check…
-
**Is your feature request related to a problem? Please describe.**
No, just would love not having to leave Lazygit. 😊
**Describe the solution you'd like**
I would like a method of reviewing and submi…
-
### Problem
Linematch and diffget do not work correctly together. I use diffget to resolve merge conflicts, and with this new diffopt option, I'm not getting the expected behavior.
Since mergi…
-
Should we consider "image diffs" as part of the spec?
For most clients pulling an image, they have a very recent, slightly older version of the image. Some clients, such as those in "edge" deployme…
-
One helpful enhancement to `tskit` is to create a "brick table" from a tree sequence. A brick table is an augmented edge
table where edges are bifurcated when they have different descendants across …
-
Some textual mockups before I forget how I envision horizontal history:
(first there were odd numbers 1 3 5 7 9, then prime 2 3 5 7, then fibonnaci 1 2 3 5 8)
First, note that changes to large cod…
-
The git history is already looking a bit hairy due to merge commits. I propose that we change the github settings for this repository to default to 'rebase and merge'.
-
If a PR has several commits on the branch, `re` shows a diff that does not reflect all of the changes that make up the PR, but only a subset (the latest commit?).
This may be how git works and have…