Skip to content

Use case: large migration tracker #32

Closed

Description

@adityamukho

Summary

Add a use case: track a long refactor, such as moving every call site off an old API, as facts per commit.

The idea

A scanner finds each call site of the old API on every commit and records it with its status and owner. The store then holds the whole history of the migration.

Questions it answers

  • How many call sites remain, and how has that changed over time?
  • Did anyone add new uses of the old API after the migration started?
  • Who owns the remaining sites?

Why Minigraf fits

  • Progress and regressions are history queries.
  • Call sites link to files, modules and owners, so grouping and ownership are simple joins.
  • Small, concrete and easy to build. A good first project for someone new to Minigraf.

Suggested content

  • The idea and a short example migration
  • A fact schema (call site, file, module, owner, status, commit)
  • A query for remaining sites by owner
  • A query for sites added after a given date

Notes


Generated by Claude Code

Activity

  1. adityamukho commented on Oct 19, 2026

    @adityamukho
    ContributorAuthor

    Builds on the git sidecar idea in #34, which provides the commit and entity index this use case attaches facts to.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions