Repository navigation
MEMORY-USAGE: Share the memory usage file without blocking pushes - #9
Merged
Merged
Conversation
…shes - Exempt memories/.usage.tsv from the naming guardrail and give usage-only commits their own subject - Add a per-clone merge=union rule on sync, with a doctor warning and a Stop-hook fallback for clones without it - Autostash the SessionStart pull and stop reporting fresh usage rows as lingering state
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The memory pack (mcs-cli/memory#45) now records the last day each memory was read in memories/.usage.tsv, so teams can see what nobody reads anymore. As shipped, this pack would refuse to push while that file is dirty, and two teammates reading memories on the same day would hit a rebase conflict that pauses auto-push.
The file is now exempt from the naming guardrail.
mcs syncgives each clone a union merge rule without committing anything to the team's repo. Clones that haven't re-synced resolve a usage-only conflict on their own. SessionStart keeps pulling while fresh usage rows are uncommitted, and doesn't report them as stuck state.Test plan
mcs syncon an existing project → expect "Added the merge=union rule…" once, then nothing on re-run.git/info/attributesand repeat → expect the same result, no/resolve-memoriespausemcs doctorwithout the rule → expect a warning that namesmcs sync