Repository navigation
Do not track another project's ledger or runtime lock files - #32
Merged
Merged
Conversation
A crew ledger for a different project appeared under docs/state/ from a cross-repository write, and lock files live there for the duration of one operation. Neither is content this repository owns, and both made the working tree read dirty to the release pre-flight check. The stray ledger is left on disk rather than removed; it is another session's artifact to triage.
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.
Two paths under
docs/are not content this repository owns, and both made the working tree read as dirty to the release pre-flight check.docs/state/imas-codex/is a crew ledger for a different project, left by a cross-repository write. Each project's ledger belongs under its own repository, and this repository already tracks its own atdocs/state/imas-standard-names/. The stray file is left on disk rather than removed — it is another session's artifact to triage, not this change's business.docs/.reckon/locks/holds lock files that exist for the duration of a single operation.No tracked file changes.