Monorepo for Tangled tangled.org

Deleting a label definition permanently retires its slug #4794

Open opened by spencergilbert.dev
assigned to boltless.me

Summary #

Deleting a label definition in repository settings permanently retires its slug. The definition cannot be recreated under the same name, the delete gives no warning, and existing issue references are left dangling.

Attempting to recreate the label produces a conflict such as:

a label def was erased at at://did:plc:.../org.tangled.label.definition/<slug>, and an erased def's slug stays retired while the versions stay in the change graph

Steps to reproduce #

  1. In repository settings, create a label definition, for example example.
  2. Apply it to an issue.
  3. Delete the definition.
  4. Try to create example again.
  5. Observe the conflict; the original issue reference renders empty or dangling.

Expected #

At minimum, deleting should warn that:

  • the slug is permanently retired and cannot be reused;
  • existing applications of the label will be dropped;
  • recovery requires choosing a new slug, with no built-in migration.

Better: make deletion reversible, or allow restoring the erased definition / creating a new definition with the same name.

Actual #

Deletion looks like an ordinary destructive action. There is no warning that it is irreversible. The slug stays retired, the old versions remain in the change graph, and the UI offers no recovery path. A later label edit drops the dangling references with a warning.

Impact #

A mistaken delete makes a common label name unusable forever. Existing automation, filters, and cross-repo references break, and the only workaround is inventing a new slug and migrating references manually.

Not specific to any one label; observed after deleting a repository's own label.

Environment #

Tangled web UI.

Sign up or Sign in to add to the discussion.