Permissions of skipped jobs still necessary on calling job

[steilerDev]

Select Topic Area

Bug

Body

Based on a CodeQL report, I've recently reduced permission scope of my jobs. Unfortunately it seems that permissions of the calling job are still required, even though the jobs requiring the permissions are skipped.

For now I'm working around this problem by increasing the scope of the permissions, but I'd like to limit permissions scope as narrowly as possible.

Details

I've got a workflow that triggers on every PR as well as one that triggers on every push - both of them call a "Build and release" workflow with different parameters:

• The PR workflow triggers the Build and Release workflow with the parameter release = false
• The Push workflow trigger the Build and Release workflow with the parameter release = true

Depending on this parameter, the release jobs in the Build and Release workflow will be skipped - the build jobs that are always triggered (1, 2 & 3) don't require any permissions, however the release workflows (1, 2, 3 & 4) (which will only be triggered if release = true) need various permissions.

To reduce the permission scope as much as possible, I therefore wanted to remove all permissions from the PR workflow and only apply the necessary permissions on the Push Workflow.

Unfortunately with this setup calling the Build and Release workflow from the PR workflow fails with:

Invalid workflow file: .github/workflows/event_pr.yml#L13](https://github.com/steilerDev/icloud-photos-sync/actions/runs/14085122975/workflow)
The workflow is not valid. .github/workflows/event_pr.yml (Line: 13, Col: 3): Error calling workflow 'steilerDev/icloud-photos-sync/.github/workflows/artifacts_build-release.yml@3e1bf9d9f32bb9b33ee22e9c9aa8696d5dc2d1b7'. The nested job 'app-release' is requesting 'contents: write, id-token: write', but is only allowed 'contents: none, id-token: none'. .github/workflows/event_pr.yml (Line: 13, Col: 3): Error calling workflow 'steilerDev/icloud-photos-sync/.github/workflows/artifacts_build-release.yml@3e1bf9d9f32bb9b33ee22e9c9aa8696d5dc2d1b7'. The nested job 'docker-release' is requesting 'contents: write', but is only allowed 'contents: none'.

It seems permission analysis is done statically and is not allowing dynamic permissions. Is this the intended behaviour?

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