Repository navigation
fix(docs): keep Action records out of clones - #31
Conversation
Publication checks failed on internal release records and forbidden phrases in public files. Preserve those records locally, keep the README prohibition test explicit, and reword descriptions without changing Action behavior.
SkillTrust — Clean — no findingsSkillTrust check passes — no findings. If this check is required, failure blocks merging. Comparison off; new, existing and fixed status is unknown. Next: No finding remediation is needed in the scanned scope. Review the rest of the PR as usual. Current findings (0)None. Grades for the current scanGrades describe findings, not whether this check fails. The policy above determines the check result.
Scan details and scope
Supported boundarySkillTrust checks supported agent configuration files in the selected scope. A clean result means no supported rule matched; it is not a guarantee that the repository is safe. Complete resultThe validated, unmodified JSON is retained at the SkillTrust Action docs · scan-action@v1 · Detector 0.12.1 |
Summary
Checks
make verify-clonepasses against local commits in all three repositories; it checks tracked files and relative links in fresh clones.Publication cleanup cannot remove historical commits already fetched.
Amp thread: https://ampcode.com/threads/T-01a0e497-3af5-777e-a9af-278e87e7c9d6