ObsolotCode migration tracking with a live picture of what's left
Migrations fail quietly. The work is announced, a few teams do it, and the rest of the estate keeps compiling against the old thing until someone tries to delete it and the build breaks.
Obsolot treats migration progress as a first-class concern rather than something you reconstruct from memory at the end.
Progress you can point at
Every deprecation notice carries a live count of remaining code references, broken down by repository. That number moves as your repositories change, because it is derived from code-search jobs rather than self-reported status.
A migration is complete when the references reach zero, not when the ticket is closed.
Discovery that keeps running
Integrations with GitHub and GitLab let Obsolot re-run discovery continuously. New usages introduced after the deprecation was announced — the ones that quietly undo your progress — are found the same way the original ones were.
Review, don't search
AI-generated migration suggestions are queued for approval, so the human effort goes into judging proposed changes rather than locating the code. Suggestions can also be authored manually when the fix needs a person's judgment.
Wire it into what you already run
Outgoing webhooks fire on entity changes, so a CI/CD pipeline or notification service can react to migration progress. Notices link to GitHub Issues and Jira, and public badges expose a repository's deprecation count inline in its README.
More on how notices are structured on the deprecation management page, or see the plans.