Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Side-by-side diff squeezes the "N unmodified lines" divider into the line-number column

Open Beginner friendly
#17,157 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in the apps/web diff UI and compare how the “N unmodified lines” divider is rendered in unified and side-by-side views. Reproduce with collapsed unchanged lines in the PR pane’s Code tab, then check the divider’s width and styling. Done when side-by-side view shows the full label and divider line with matching line and hover styling.

Written by the indexing model from the issue text.

Description

bug via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Open a diff with collapsed unchanged lines, for example in the PR pane's Code tab.
  2. Switch to side-by-side view.
  3. Look at the divider between two hunks.
Expected behavior

The divider spans the full width and reads "2 unmodified lines", with the same line and hover styling as in the unified view.

Actual behavior

The label is squeezed into the left line-number column and cut off to "2 u". The rest of the row is blank, with no divider line.

Impact

Cosmetic issue

Version or commit

0.0.46-nightly.20261008.2813

Environment

macOS, desktop app

Screenshots, recordings, or supporting files
Image
Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
13h 9m
Merged PRs (30d)
271

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.