"Workflow file" button should link to reusable workflow source, not parent workflow

[mildmojo]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

General

Discussion Details

I have many private repos with a top-level orchestration GitHub Actions workflow at .github/workflows/all.yaml. That workflow calls a number of other workflows in the same folder, like deploy.yaml.

Problem

all.yaml calls deploy.yaml. When viewing the run logs for deploy.yaml, the sidebar "Workflow file" link goes to the source for the caller (all.yaml), not the workflow I'm looking at (deploy.yaml).

When viewing job logs, the sidebar link should always view the source for the workflow file that generated the logs on screen. Or, there should be another link in the page to navigate to that file. It's very disorienting to be taken to another workflow file altogether, which does not contain the code that generated the logs I was viewing.

As a workaround, I've added a job to all of my top-level GHA workflows that uses $GITHUB_STEP_SUMMARY to show links to view source on the current branch for all files that the workflow calls. But that still requires leaving the job log view to go back to the run summary to get to those links.

Reproduction

1. Trigger the workflows below.
2. Visit the workflow run summary page, and click on the deploy job in the graph to view its logs.
3. Click the Workflow file link in the sidebar while viewing the deploy logs.
4. Observe that you're taken to the source for all.yaml, not deploy.yaml.

name: all.yaml

on:
  workflow_dispatch:
  push:

jobs:
  deploy:
    uses: ./.github/workflows/deploy.yaml

name: deploy.yaml

on:
  workflow_call:

jobs:
  deploy_to_prod:
    runs-on: ubuntu-latest
    steps:
      - run: |
          echo "## Deployment job complete" > $GITHUB_STEP_SUMMARY

Annotated screenshot of log view for deploy.yaml in a similar setup

Annotations in yellow boxes describe where the links will take you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐