Skip to content

state-mgmt: Restructure, and document state remove#95

Merged
CookieSource merged 2 commits intomainfrom
moss/state-remove-ranges
Mar 12, 2026
Merged

state-mgmt: Restructure, and document state remove#95
CookieSource merged 2 commits intomainfrom
moss/state-remove-ranges

Conversation

@ermo
Copy link
Member

@ermo ermo commented Mar 12, 2026

The flow now more closely matches what a new user might want to actually do with moss, and does so in a way that foreshadows the state concept.

Resolves #94

The flow now more closely matches what a new user might want to actually
do with moss, and does so in a way that foreshadows the state concept.

Signed-off-by: Rune Morling <ermo@aerynos.com>
@ermo ermo force-pushed the moss/state-remove-ranges branch from 99df93b to 5f8b132 Compare March 12, 2026 10:33
@CookieSource CookieSource self-requested a review March 12, 2026 14:51
Copy link
Member

@CookieSource CookieSource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good I think we should switch to programname or instead of random package names for a clearer message.

Signed-off-by: Rune Morling <ermo@aerynos.com>
@ermo ermo requested a review from CookieSource March 12, 2026 15:06
@CookieSource
Copy link
Member

LGTM!!

@CookieSource CookieSource merged commit 3bef46a into main Mar 12, 2026
1 check passed
@CookieSource CookieSource deleted the moss/state-remove-ranges branch March 12, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add new state range remove capability

2 participants