Skip to content

Track historical local-path strings in pre-existing main commits #6

Description

@falltwo

Context

The tiered-access work found 14 Windows local-path strings across five commits that already exist in the public main history.

Current state

  • The current branch tip and all additions made by the tiered-access branch are clean.
  • The current-tip copies of the affected documentation/scripts no longer contain those local paths.
  • Gitleaks v8.30.1 reported zero secret findings in both repository history and the working tree.
  • The historical strings are local filesystem paths, not confirmed secrets.

Follow-up decision

The repository owner should decide separately whether rewriting already-public history is warranted. Do not rewrite history as part of the tiered-access pull request.

Acceptance criteria

  • Review the five historical commits and classify the path disclosures.
  • Document whether leaving history unchanged is acceptable.
  • If rewriting is justified, plan it as a separately approved migration with collaborator coordination and rollback instructions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions