tkt 0.1.0

Git-native ticket CLI — frontmatter-driven work tracking in .tickets/
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

//! `tkt renumber` — move a ticket to a new ID atomically.

use anyhow::Result;

use crate::commands::common::{domain_bail, is_quiet, success_msg};
use crate::core::validate;
use crate::mutation::MutationContext;
use crate::renumber::{apply_renumber, RenumberPlan};

pub fn run(old_id: &str, new_id: &str, file_hint: Option<&str>) -> Result<i32> {
    if let Err(e) = validate::validate_id(new_id) {
        domain_bail!("new id: {}", e);
    }

    let ctx = MutationContext::open()?;

    // Plan
    let plan = RenumberPlan::single(&ctx.corpus, old_id, new_id, file_hint)
        .map_err(|e| crate::DomainError(e.to_string()))?;

    // Apply
    let result = apply_renumber(&ctx.tickets_dir, &plan)?;

    // Publish
    let path_refs: Vec<&str> = result.staged_paths.iter().map(|s| s.as_str()).collect();
    ctx.publish(
        &path_refs,
        &format!("chore(tickets): renumber {} -> {}", old_id, new_id),
    )?;

    // Report
    if !is_quiet() {
        let detail = if result.refs_updated > 0 {
            format!("{} refs updated", result.refs_updated)
        } else {
            String::new()
        };
        println!(
            "{}",
            success_msg("renumbered", old_id, &format!("→ {}", new_id), &detail)
        );
    }
    Ok(0)
}