Bug where the on.push.paths filter does not function

[huuyafwww]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

Hello, I'm currently actively using GitHub Actions for my project.
I want to trigger the workflow only when the actions workflow is modified using the on.push.paths filter in Actions, but it triggers on every push.
The full workflow is as follows.

name: Check Pinned Actions

on:
  push:
    paths:
      - '.github/workflows/**'

jobs:
  check-pinact:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0

      - name: Run pinact and fail on diff
        uses: suzuki-shunsuke/pinact-action@49cbd6acd0dbab6a6be2585d1dbdaa43b4410133 # v1.0.0
        with:
          skip_push: “true”

This workflow is designed to address recent security issues by verifying whether an action's version is fixed via checksum.
Therefore, it should only detect changes to .github/workflows/** and trigger then. However, it will also be triggered if a commit that does not match the paths rules is pushed.

Please verify why the paths rule detecting changes to workflow files like .github/workflows/** is not functioning.
If there is a workaround, please let me know that as well.

This workflow appears to function without issues, but when actually run, it triggers on every push regardless of the paths rules. Please verify this behavior.

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