{"version":"2.1.229","anchor":"attribution-and-includecoauthoredby-no-longer-raise-settings","canonical_anchor":"attribution-and-includecoauthoredby-no-longer-raise-settings","heading":"attribution and includeCoAuthoredBy no longer raise settings-conflict warnings","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/attribution-and-includecoauthoredby-no-longer-raise-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### `attribution` and `includeCoAuthoredBy` no longer raise settings-conflict warnings\n\nSetting commit attribution in more than one place no longer triggers a conflict warning.\n\n**What**\n\nThese two settings are now excluded from the check that warns when a managed or inline setting conflicts with your own, so setting commit attribution in more than one place stops producing a warning.\n\n**Details**\n\n- The attribution settings object now accepts extra keys rather than rejecting them.\n- New helpers derive the commit trailer state from that object as explicitly enabled, implicitly enabled, or disabled.\n\n**Evidence**\n\n`e !== \"attribution\" && e !== \"includeCoAuthoredBy\"`\n\n- Area: Settings\n- Names: `attribution`, `includeCoAuthoredBy`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}