Seen on: component/git-history
What it fixes
T3 Code cannot show a repository's history. Our Git History view exists only on a fork branch, about 4,000 source lines mixing server, contracts, and UI. Upstream just closed the 40,000-line issues PR we had stacked it on as too big to review, and ours would get the same answer. Fork-only means rebasing forever, and nobody else gets the feature.
Why we need it
A series of small PRs only works if the end state is clear from the first one. The first PR is server-only and invisible, so without a stated goal it reads as pointless machinery. This issue is that goal. Every piece, and every PR description, links back to it.
How to fix it
End state: a Repository pane beside the thread with History, Issues, and Pull Requests tabs, scoped to the project and environment, working over remote connections, with History usable on its own before upstream's issues workspace lands. Delivered as eleven self-contained PRs, each a few hundred source lines, in order: three server PRs (commit pages and commit details; branch and tag pages; changed files and diff), five web PRs (a plain History tab; the commit graph; the details pane; the branches pane with favorites; the diff view), and three pane PRs (a Pull Requests tab beside the thread; the Repository pane hosting History and Pull Requests; the Issues tab once upstream has an issues workspace). Each PR's description carries this end state and its place in the series. The four known defects on the fork branch are fixed inside the piece they belong to, never carried along.
Seen on: component/git-history
What it fixes
T3 Code cannot show a repository's history. Our Git History view exists only on a fork branch, about 4,000 source lines mixing server, contracts, and UI. Upstream just closed the 40,000-line issues PR we had stacked it on as too big to review, and ours would get the same answer. Fork-only means rebasing forever, and nobody else gets the feature.
Why we need it
A series of small PRs only works if the end state is clear from the first one. The first PR is server-only and invisible, so without a stated goal it reads as pointless machinery. This issue is that goal. Every piece, and every PR description, links back to it.
How to fix it
End state: a Repository pane beside the thread with History, Issues, and Pull Requests tabs, scoped to the project and environment, working over remote connections, with History usable on its own before upstream's issues workspace lands. Delivered as eleven self-contained PRs, each a few hundred source lines, in order: three server PRs (commit pages and commit details; branch and tag pages; changed files and diff), five web PRs (a plain History tab; the commit graph; the details pane; the branches pane with favorites; the diff view), and three pane PRs (a Pull Requests tab beside the thread; the Repository pane hosting History and Pull Requests; the Issues tab once upstream has an issues workspace). Each PR's description carries this end state and its place in the series. The four known defects on the fork branch are fixed inside the piece they belong to, never carried along.