/etc/nginx is its own area in alerts. dejima documents it for remote access on the devbox, so changes there are common and expected. They now read as file(s) modified in /etc/nginx rather than as /etc, which says straight away which feature they belong to. The path itself is still never sent; the label comes from the guard's fixed list.
The known_hosts note is accurate. It said known_hosts changes only when the devbox first connects to an SSH host. ssh's UpdateHostKeys, on by default, also adds keys an already-known host offers and keeps the previous file as known_hosts.old, so a familiar forge can change it too, as two files. The push note, README and config example now say both.
Tested: bats test/, all passing, with a new test for the nginx area. shellcheck clean.
**Summary generated by LLM agent**
Follow-up to #27.
**`/etc/nginx` is its own area in alerts.** dejima documents it for remote access on the devbox, so changes there are common and expected. They now read as `file(s) modified in /etc/nginx` rather than as `/etc`, which says straight away which feature they belong to. The path itself is still never sent; the label comes from the guard's fixed list.
**The known_hosts note is accurate.** It said known_hosts changes only when the devbox first connects to an SSH host. ssh's `UpdateHostKeys`, on by default, also adds keys an already-known host offers and keeps the previous file as `known_hosts.old`, so a familiar forge can change it too, as two files. The push note, README and config example now say both.
Tested: `bats test/`, all passing, with a new test for the nginx area. shellcheck clean.
dejima documents /etc/nginx for remote access on the devbox, so a change
there is common and now reads as its own area rather than as /etc.
The known_hosts note said it changes only on a first connection. ssh's
UpdateHostKeys also adds keys a known host offers, keeping known_hosts.old.
branderson
approved these changes 2026-10-15 16:10:09 -07:00
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.
Summary generated by LLM agent
Follow-up to #27.
/etc/nginxis its own area in alerts. dejima documents it for remote access on the devbox, so changes there are common and expected. They now read asfile(s) modified in /etc/nginxrather than as/etc, which says straight away which feature they belong to. The path itself is still never sent; the label comes from the guard's fixed list.The known_hosts note is accurate. It said known_hosts changes only when the devbox first connects to an SSH host. ssh's
UpdateHostKeys, on by default, also adds keys an already-known host offers and keeps the previous file asknown_hosts.old, so a familiar forge can change it too, as two files. The push note, README and config example now say both.Tested:
bats test/, all passing, with a new test for the nginx area. shellcheck clean.