pull_request_target changes still leave confusing File not found for Workflow file

[jsoref]

Select Topic Area

Bug

Body

github/docs@bcff1fe is an interesting change.

It appears to be at least somewhat live on GitHub as I believe https://github.com/check-spelling-sandbox/archiver-utils/actions/runs/20178903457?pr=1 ran based on the default branch (the code isn't present in the base branch).

As before, the Workflow file link doesn't work:

Workflow file for this run
.github/workflows/spelling.yml at 8e3765d
File not found
The workflow file could not be found.

Also note that the space after yml in the file path is linked resulting in an ugly underlined space. The space should be after the link, not before -- like this:

.github/workflows/spelling.yml at 8e3765d

---

p.s. I hope someone plans to announce these changes.

[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. ⭐