{"version":"2.1.309","anchor":"ref-and-cloud-validation-code-touched","canonical_anchor":"ref-and-cloud-validation-code-touched","heading":"No visible change to the --ref and --cloud checks","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/ref-and-cloud-validation-code-touched","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### No visible change to the `--ref` and `--cloud` checks\n\nThe checks behind `--ref` and `--cloud` were reworked internally; they behave the same and show the same error messages\n\n**What**\n\nThe code that checks the `--ref` and `--cloud` options was reworked internally. The checks behave as before, and the error messages are word for word the same, including \"--ref requires a non-empty branch, tag, or SHA\".\n\n**Why**\n\nNothing changes for anyone using these options, so there is nothing to do.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}