Scheduled automation fails when a non-default branch is checked out locally

Describe the bug

A scheduled repository automation fails when the associated local clone is currently checked out to a branch other than the workflow/default branch. The failure instructs the user to switch the local clone back to the expected branch before rerunning the workflow.

A scheduled automation should not depend on whichever branch happens to be checked out in a mutable local working copy. This makes schedules unexpectedly brittle and allows unrelated local development activity to break them.

Affected version

No response

Steps to reproduce the behavior

1. Configure a scheduled automation for a repository while its workflow/default branch is selected.
2. In the associated local clone, check out a different branch for unrelated work.
3. Allow the scheduled automation to run.
4. Observe that it fails because the workflow/default branch is not currently checked out locally.

Expected behavior

Scheduled automations should run against the configured workflow branch or repository default branch regardless of the local clone's currently checked-out branch. If a local checkout is required, Copilot should use an isolated worktree/clone or safely resolve the configured branch without requiring the user's active working tree to switch branches.

Additional context

The visible error explicitly says the workflow branch is not checked out and asks the user to switch branches in the local clone. Identifying repository, branch, organization, and automation names have been intentionally omitted. The original screenshots contain those details and should not be attached without redaction.

Aucun fichier source ni test n’est indiqué. Commencez par reproduire une automatisation planifiée avec une branche non par défaut extraite localement, puis suivez la gestion par la CLI du workflow configuré ou de la branche par défaut et de la copie de travail locale. Le travail est considéré comme terminé lorsque l’automatisation s’exécute sans nécessiter que le checkout actif de l’utilisateur change de branche, avec une couverture du scénario signalé.