Conversation
debug PR head and runid
There was a problem hiding this comment.
Pull request overview
Updates the PR test workflow to print additional GitHub context for debugging which commit/repo is being executed.
Changes:
- Add a debug/PoC step to echo PR head repo, PR head SHA, and the workflow run id.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - name: PoC: confirm PR head executed | ||
| run: | | ||
| echo "PR head repo: ${{ github.event.pull_request.head.repo.full_name }}" | ||
| echo "PR head sha: ${{ github.event.pull_request.head.sha }}" | ||
| echo "Run id: ${{ github.run_id }}" |
There was a problem hiding this comment.
This step uses github.event.pull_request.* directly, but the workflow is also triggered by merge_group (see top of file). On merge_group runs these fields will be empty/undefined, so the output won’t accurately reflect what was checked out. Consider either guarding this step with if: github.event_name == 'pull_request' or using the same fallback expressions used by actions/checkout (e.g., ...head.repo.full_name || github.event.repository.full_name and ...head.sha || github.sha).
| - name: PoC: confirm PR head executed | ||
| run: | | ||
| echo "PR head repo: ${{ github.event.pull_request.head.repo.full_name }}" | ||
| echo "PR head sha: ${{ github.event.pull_request.head.sha }}" | ||
| echo "Run id: ${{ github.run_id }}" |
There was a problem hiding this comment.
This appears to be a temporary PoC/debug logging step. If it’s only needed for short-term troubleshooting, consider removing it once validated, or gating it behind an input/env flag to avoid adding log noise to every PR run.
| - name: PoC: confirm PR head executed | |
| run: | | |
| echo "PR head repo: ${{ github.event.pull_request.head.repo.full_name }}" | |
| echo "PR head sha: ${{ github.event.pull_request.head.sha }}" | |
| echo "Run id: ${{ github.run_id }}" |
debug PR head and runid
WHY are these changes introduced?
Fixes #0000
WHAT is this pull request doing?
How to test your changes?
Post-release steps
Measuring impact
How do we know this change was effective? Please choose one:
Checklist