Skip to content

Track unmerged branches that have no issue (2) #512

Open

Description

@woksin

These branches in Cratis/Components hold unmerged work that no issue tracks. None of it is merged or part of any release. Each needs a decision: open a focused issue and finish it, fold it into an existing issue, or delete the branch.

Work that still applies to main

  • feature/schema-editor-tree (7 commits, last 2026-10-06): Replaces table SchemaEditor with tree editor; contrast, renderer matrix, host adaptation specs Remaining: Not merged; main lacks Migration/4-to-5 docs

Needs a closer look

The purpose or relevance of these could not be confirmed from the commits alone.

Check an item off once it has its own issue, has been merged or the branch has been deleted.

Activity

  1. self-assigned this
    on Nov 21, 2026
  2. woksin commented on Nov 21, 2026

    @woksin
    ContributorAuthor

    The documentation remainder from the CommandDialog snapshot is released in v4.56.0 (#571): the CommandDialog pages now explain that the busy state ends before result callbacks run, and what happens when a result callback rejects. The tree editor branch stays superseded by the additive SchemaEditor layout from #407, so neither stale branch should be merged; what remains here is deciding the disposition of the listed branches.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions