{"version":"2.1.234","anchor":"git-mutation-event-now-documents-what-it-can-and-cannot-prov","canonical_anchor":"git-mutation-event-now-documents-what-it-can-and-cannot-prov","heading":"Git-mutation event now documents what it can and cannot prove","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/git-mutation-event-now-documents-what-it-can-and-cannot-prov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Git-mutation event now documents what it can and cannot prove\n\nThe internal repo-change event now documents what it can and cannot actually prove.\n\n**What**\n\nThe internal event fired when a shell command may have changed a repository has clearer documentation of its own limits.\n\n**Details**\n\n- `cwd` is defined as the directory the shell was in when the command finished, so an inner `cd` is reflected but a `git -C` target is not.\n- A foreground push whose ref output was redirected still emits the event on the invoking command's zero exit code alone; the documentation now states the event is a prompt to look, never a claim that something changed.\n\n**Evidence**\n\n`the event is a prompt to look, never a claim`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}