{"version":"2.1.312","anchor":"publish-refusal-advisory-depends-on-forcerefused","canonical_anchor":"publish-refusal-advisory-depends-on-forcerefused","heading":"Advice shown after a rejected publish now depends on whether forcing was refused","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/publish-refusal-advisory-depends-on-forcerefused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Advice shown after a rejected publish now depends on whether forcing was refused\n\nWhen a publish is rejected because of a conflict, the closing advice now differs depending on whether a forced publish was refused\n\n**Unclear.** Which Claude Code feature this publish step belongs to is not known.\n\n**What**\n\nWhen something you publish is rejected because of a conflict, the end of the message used to be built from the reason given. It now picks one of two fixed endings, depending on whether a forced publish was refused. Guidance such as merging your edits on top and then publishing again is part of this advice.\n\n**Why**\n\nThe guidance you see after a rejected publish may be worded differently.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}