[jeffhandley]

Summary

Fix the Labeler: Promotion workflow failing at the "Delete Existing Active Cache Entry" step.

Cause

The promote/action.yml composite action invokes gh cache delete without a checkout, so gh has no git remote from which to infer the target repository and exits before making the API call:

gh cache delete "issue-labeler/model/issues/ACTIVE"
failed to determine base repo: failed to run git: fatal: not a git repository (or any of the parent directories): .git
##[error]Process completed with exit code 1.

Observed in consumer runs such as microsoft/aspire #23395851258 and dotnet/sdk #17777754813. This is not a permissions issue — actions: write and GH_TOKEN are already set; gh fails before reaching the API.

Change

• Add GH_REPO: ${{ github.repository }} to the env block of the "Delete Existing Active Cache Entry" step in promote/action.yml.

Impact

• Consumers reference dotnet/issue-labeler/promote@main and need no changes on their side.
• No behavior change for gh cache delete other than restoring the ability to resolve the target repository.

[Copilot]

Pull request overview

This PR fixes the Labeler: Promotion workflow failure in the promote composite action by ensuring gh cache delete can resolve the target repository even when no repository checkout is present (no .git directory to infer the remote).

Changes:

• Set GH_REPO to ${{ github.repository }} for the cache-deletion step so gh can determine the base repo.
• Restore successful execution of the “Delete Existing Active Cache Entry” step in consumer workflows.