Skip to content

enhancement: Store PR number as first-class field in oplog #153

@erishforG

Description

@erishforG

Problem

PR number/URL extraction from oplog uses fragile detail.split(" -> ").nth(1) + rsplit('/').next()?.parse::<u64>() pattern, repeated 7+ times across commands.rs.

Proposed Solution

Add pr_number: Option<u64> and pr_url: Option<String> to OpEntry or UndoInfo. Eliminates a whole class of parsing bugs. Backward-compatible with existing oplog entries via #[serde(default)].

Category: enhancement | Priority: high

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions