{"version":"2.1.290","anchor":"cloud-session-hookcapture-refusal-messages-reworded-path-t","canonical_anchor":"cloud-session-hookcapture-refusal-messages-reworded-path-t","heading":"Clearer reason when a git config include blocks a cloud session capture","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-session-hookcapture-refusal-messages-reworded-path-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer reason when a git config include blocks a cloud session capture\n\nA cloud session refusal about git configuration is reworded, and a message about trimmed search path entries now gives the right count\n\n**Unclear.** Which feature shows these messages to users is not known.\n\n**What**\n\nWhen a cloud session refuses to run a capture because of how a checkout's git configuration is set up, the reason is now worded: \"a cloud session could change a file that git reads this checkout's configuration from, so that capture would run under whatever is put there\". Before, it spoke of the git configuration including a file a session can write.\n\nA separate message about trimmed entries in the search path now reports the number of entries that were actually trimmed.\n\n**Why**\n\nOnly the wording and a count changed. What is refused stays the same, but the messages are easier to act on and the count is now correct.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}