Skip to content

chore(upstream): track the pull request state icons - #527

Merged
incognitojam merged 1 commit into
mainfrom
styal/show-pr-status-icons
Sep 29, 2026
Merged

incognitojam merged 1 commit into
mainfrom
styal/show-pr-status-icons

Conversation

@incognitojam

Copy link
Copy Markdown
Owner

The pull request badge in the sidebar and composer uses the same icon for every state, so draft, closed and merged pull requests differ only by colour. Upstream fixed this in pingdotgg#11144, which gives each state its own icon: open, draft, closed and merged. A stack keeps the layers icon.

This PR adds pingdotgg#11144 to .github/upstream-tracked-prs.json. It was merged upstream on 2026-09-16 and is not yet on main or any intake branch. node scripts/upstream-tracked-prs-report.ts lists it as pending, 5.9 days ahead of the fork tip, and scripts/upstream-tracked-prs.test.ts passes.


Written by an agent (Claude Code, claude-opus-5-5).

@incognitojam
incognitojam merged commit a1c73e0 into main Sep 29, 2026
24 checks passed
@incognitojam
incognitojam deleted the styal/show-pr-status-icons branch September 29, 2026 09:59
incognitojam added a commit that referenced this pull request Sep 29, 2026
Release notes listed every commit since the previous release, so docs,
CI, and intake bookkeeping commits such as #527 appeared next to app
changes. The desktop update popover renders the same notes, so users saw
them there too.

## Change

`render_release_notes` now lists a commit only when it changes shipped
code: a file under `apps/web`, `apps/desktop`, `apps/mobile`,
`apps/server`, `packages/`, or `patches/`, excluding tests, test
fixtures and helpers, `scripts/` folders, integration suites, and
Markdown. The remaining commits are counted on the Full Changelog line:

```
**Full Changelog**: https://github.com/incognitojam/styal/compare/…430...…431 (includes 6 docs, CI, test, and tooling changes not listed above)
```

The desktop updater already skips the Full Changelog line, so the count
does not appear as a change in the popover. Nightly and stable releases
share the renderer, so both get the filter.

The rule uses changed paths rather than the commit subject. #38 removed
an earlier subject-based filter because it could hide user-facing
changes made in `ci` or release commits; with paths, a `ci(release)`
commit that changes desktop code is still listed. Relay changes are not
listed because the relay deploys from `main` through `deploy-relay.yml`,
not with releases.

## Validation

- Rendered notes with the new function against the real tags for three
published nightlies and compared them with the published bodies:
- `v0.1.0-nightly.20260928.430`: only the web fix (#503) remains;
`docs(agents)` #505 and `chore(upstream)` #506 are counted instead.
- `v0.1.0-nightly.20260928.431`: 6 commits dropped, all `ci` and
`chore(upstream)`, including #527.
- `v0.1.0-nightly.20260926.422`: 15 dropped. Apart from docs, CI, tests,
and intake bookkeeping, these are three `infra/relay` fixes and two
upstream macOS installer artwork cherry-picks that are empty in the fork
(their intake notes say "Not applied"), so the published notes listed
changes that were not in the build.
- Ran the rendered notes for nightly 430 through
`normalizeDesktopUpdateReleaseNotes`, as Markdown and as GitHub-rendered
HTML. Both produce the single listed change and no count item.
- `vp test run scripts/release-changelog.test.ts` (36 passed): path
classification cases, a mixed fork and upstream render with the omitted
count, and a release where every commit is internal.
- Not verified: a full nightly or stable workflow run with this change.

Still listed: version bump commits (`chore(release): prepare …`,
`chore(mobile): bump app version`) and refactors, because they change
app files. Commits that change only the lockfile are not listed.

---
Written by an agent (Claude Code, claude-opus-5-5).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant