Replies: 4 comments
-
We are currently experiencing the same behavior. We have a similar configuration where we want to trigger an action on pull-request with three paths set as filter. When i manually create a PR with a lot of new/changed files (more than 300 in this case) the action is not triggering. Can some help? P.S. In our special case we have only one file which is changed which matches one of the paths filters and the rest of the files are not matching any path filter. |
Beta Was this translation helpful? Give feedback.
-
Hello, GitHub Community. I recently seem to have encountered the same/similar issue. Related to: dorny/paths-filter#227 Originally, I was using
From the log output, it seems that: The PR contains too many files changed, so that |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I'm seeing this as well on PRs with large numbers of files |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Description:
I have encountered a bug in GitHub Actions where actions that run only when files are changed in a certain path do not run when many files are modified. This issue severely affects the functionality and reliability of workflows, especially in cases where required tests are not run.
Steps to Reproduce:
` pull_request:
paths:
Expected Behavior:
The workflow should trigger and execute all the actions regardless of the number of files changed.
Actual Behavior:
When a large number of files are modified, the action does not execute.
Additional Information:
This issue is more pronounced when the number of modified files exceeds a certain threshold, although the exact limit is uncertain.
Workaround:
Currently, there is no reliable workaround to ensure the execution of actions on all modified files when a large number of files are changed. One possible workaround is to split the changes into smaller prs. However, this is an inconvenient and time-consuming solution, especially in cases where the workflow's success depends on processing all the changes together.
Impact:
The bug significantly impacts developers who rely on GitHub Actions to automate their workflows. It hinders productivity, introduces inconsistencies, and undermines the reliability of the development process.
Beta Was this translation helpful? Give feedback.
All reactions