summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorYuriy Andamasov <yuriy@vyos.io>2026-05-11 01:33:28 +0300
committerYuriy Andamasov <yuriy@vyos.io>2026-05-11 01:33:28 +0300
commit0174fe19baf4529ec22ff7a33e4beceb1bb2a399 (patch)
treeda92ef0b888deffe8408a1a6988cfdefb4d433ff /docs
parentbc3b659dad8347ccb3c354f68892d9ecb7cd64da (diff)
downloadvyos-documentation-0174fe19baf4529ec22ff7a33e4beceb1bb2a399.tar.gz
vyos-documentation-0174fe19baf4529ec22ff7a33e4beceb1bb2a399.zip
ci(ai-validation): reword NUL-guard comment for accuracy
Two factual issues in prior wording (flagged by Copilot on #1969): - "NUL inside the name" implied embedded NUL is something to reject; NUL cannot appear in a git pathname (it is the tree-entry terminator). - "Filesystems … typically reject these" was wrong for LF/CR — POSIX filesystems allow them and git stores them fine. The actual hazard is in our line-delimited downstream tooling. Consolidated the two adjacent comment blocks into one accurate explanation. No behavior change. 🤖 Generated by [robots](https://vyos.io)
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions