forge issue view and pr view: print created, updated, closed, and merged timestamps #194

Closed
opened 2026-09-10 23:04:44 +01:00 by allod-agent · 0 comments
Member

Show when an issue or pull request was opened, last updated, closed, and merged, so age-based triage can be read from forge output instead of being bracketed from the commit dates of neighbouring pull requests.

Primary goals:

  • Timestamps in the view header — forge issue view and forge pr view print Created: and Updated: lines beside State: and Author:, plus Closed: when closed.
  • Merge state on pull requests — forge pr view prints Merged: yes <date> or Merged: no for a closed pull request, and the pr snapshot JSON carries the same fields.
  • Dates as ISO days — the same YYYY-MM-DD form the comment lines already use, so a script can compare them without parsing prose.

Current state and specifics

Both view commands print State, Author, Labels, Milestone, or Branch, and nothing dated. Comment lines carry [YYYY-MM-DD], so an issue's last activity is readable only when it has comments; an issue with none has no visible age at all. The forge-groom skill in allod/memory labels an item stale after 30 days without a comment or commit and surfaces decision items after 30 days open, and on 2026-09-10 both thresholds had to be approximated: an issue's creation date was bounded by the head-commit dates of the nearest lower and higher pull request numbers in the same repository, which leaves a window of weeks in sparse repositories (allod/vm, allod/secrets, allod/profiles) and no answer at all for the oldest issues.

Scope

In: the header lines of issue view and pr view, and the corresponding fields in pr snapshot. Out: dated columns in issue list and pr list, which can follow once the view output has settled; the pr list state filter and merged marker, tracked in allod/tools#193.

Show when an issue or pull request was opened, last updated, closed, and merged, so age-based triage can be read from `forge` output instead of being bracketed from the commit dates of neighbouring pull requests. Primary goals: - **Timestamps in the view header** — `forge issue view` and `forge pr view` print `Created:` and `Updated:` lines beside `State:` and `Author:`, plus `Closed:` when closed. - **Merge state on pull requests** — `forge pr view` prints `Merged: yes <date>` or `Merged: no` for a closed pull request, and the `pr snapshot` JSON carries the same fields. - **Dates as ISO days** — the same `YYYY-MM-DD` form the comment lines already use, so a script can compare them without parsing prose. ### Current state and specifics Both view commands print `State`, `Author`, `Labels`, `Milestone`, or `Branch`, and nothing dated. Comment lines carry `[YYYY-MM-DD]`, so an issue's last activity is readable only when it has comments; an issue with none has no visible age at all. The forge-groom skill in `allod/memory` labels an item `stale` after 30 days without a comment or commit and surfaces `decision` items after 30 days open, and on 2026-09-10 both thresholds had to be approximated: an issue's creation date was bounded by the head-commit dates of the nearest lower and higher pull request numbers in the same repository, which leaves a window of weeks in sparse repositories (`allod/vm`, `allod/secrets`, `allod/profiles`) and no answer at all for the oldest issues. ### Scope In: the header lines of `issue view` and `pr view`, and the corresponding fields in `pr snapshot`. Out: dated columns in `issue list` and `pr list`, which can follow once the view output has settled; the `pr list` state filter and merged marker, tracked in allod/tools#193.
vnprc closed this issue 2026-09-11 21:28:00 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
allod/tools#194
No description provided.