Skip to content

Handle slug changes more elegantly #61

Closed

Description

@Mossop

Sometimes I will change the title of a query in stmo and then fetch the change locally. This generates a duplicate of the query file with the new slug. Eventually Claude notices and decides to delete one of them. Sometimes it chooses the wrong one 😱.

The ideal would be just automatically removing the old query, but unless we know that that version has already been deployed there is a risk of losing changes. So I'm not exactly sure what the right fix is here. Perhaps some flow where stmo-cli suggests that Claude ask the user if they want to remove the old one?

Activity

  1. JohanLorenzo commented on Oct 9, 2026

    @JohanLorenzo
    Collaborator

    Thanks for filing this issue @Mossop! I gave it some thought. The easiest solution is to stop using the query title in the filename and use use the ID. That'll prevent duplication in the first place and avoid any overengineering around deduplication. #64 will take care of that.

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

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions