A separate project, tf-inspect/, sits untracked in the repo root. It has its own .git/, .gitea/, lockfiles, and .pre-commit-config.yaml — it is not part of this flake and is not referenced by it.
Impact
It shows up forever in git status as untracked noise.
It is at risk of an accidental git clean -xd wiping it (it is not committed).
It confuses the boundary of what this repo owns.
Suggested fix
Decide its home: either move it out of this working tree, or add tf-inspect/ to .gitignore if it is intentionally kept here as a local scratch checkout.
## Problem
A separate project, `tf-inspect/`, sits untracked in the repo root. It has its own `.git/`, `.gitea/`, lockfiles, and `.pre-commit-config.yaml` — it is not part of this flake and is not referenced by it.
## Impact
- It shows up forever in `git status` as untracked noise.
- It is at risk of an accidental `git clean -xd` wiping it (it is not committed).
- It confuses the boundary of what this repo owns.
## Suggested fix
Decide its home: either move it out of this working tree, or add `tf-inspect/` to `.gitignore` if it is intentionally kept here as a local scratch checkout.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
A separate project,
tf-inspect/, sits untracked in the repo root. It has its own.git/,.gitea/, lockfiles, and.pre-commit-config.yaml— it is not part of this flake and is not referenced by it.Impact
git statusas untracked noise.git clean -xdwiping it (it is not committed).Suggested fix
Decide its home: either move it out of this working tree, or add
tf-inspect/to.gitignoreif it is intentionally kept here as a local scratch checkout.