{"version":"2.1.227","anchor":"repository-mutation-events-can-name-the-branch","canonical_anchor":"repository-mutation-events-can-name-the-branch","heading":"Repository-mutation events can name the branch","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/repository-mutation-events-can-name-the-branch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Repository-mutation events can name the branch\n\nCommit events can now name the branch, as a best-effort hint from git's output.\n\n**What**\n\nThe internal event emitted when a shell command changes repository state gained an optional branch field, read from the summary line git prints for a commit. Only commit events carry it, and it is a best-effort hint that is left out whenever attribution is uncertain.\n\n**Evidence**\n\n`The branch the commit landed on`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}