{"version":"2.1.281","anchor":"attribution-setting-accepts-truefalse","canonical_anchor":"attribution-setting-accepts-truefalse","heading":"attribution setting accepts true\/false","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/attribution-setting-accepts-truefalse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### `attribution` setting accepts true\/false\n\nThe `attribution` setting now accepts `true` or `false`, and `false` hides all attribution\n\n**What**\n\nThe `attribution` setting can now be a simple true or false value instead of only a group of fields:\n\n- `false` hides all attribution. It is the same as `{ \"commit\": \"\", \"pr\": \"\", \"sessionUrl\": false }`.\n\n- `true` is the same as leaving the setting out.\n\nAn invalid value now produces its own error message. When `attribution` is `false`, merging settings from different places forces `attribution.sessionUrl` to false. The check for whether your settings configure attribution now counts `attribution: false` too, not only the object form or the deprecated `includeCoAuthoredBy`.\n\n**Why**\n\nYou can turn off every kind of attribution with one value instead of spelling out each field. A session link cannot slip back in from another settings file."}