[GH-ISSUE #454] act not honoring on.push.paths #318

Open
opened 2026-03-01 21:42:19 +03:00 by kerem · 5 comments
Owner

Originally created by @jmcarbo on GitHub (Dec 21, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/454

  • Version of act: act version 0.2.17
  • Platform: Linux, macOS
  • The complete main.workflow file used
name: bla

on:
  push:
    paths:
      - 'docs/*'

jobs:
  bla2:
    runs-on: ubuntu-latest
    steps:
      - run: echo hello world
  • The complete command that was executed
    act -r

Any output from the command

[bla/bla2] 🚀 Start image=node:12.6-buster-slim
[bla/bla2] 🐳 docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[bla/bla2] Run echo hello world
| hello world
[bla/bla2] Success - echo hello world

Desired behaviour:

The second time the command is run it should no run because no changes were made to docs/* files.

Originally created by @jmcarbo on GitHub (Dec 21, 2020). Original GitHub issue: https://github.com/nektos/act/issues/454 * Version of act: act version 0.2.17 * Platform: Linux, macOS * The complete main.workflow file used ``` name: bla on: push: paths: - 'docs/*' jobs: bla2: runs-on: ubuntu-latest steps: - run: echo hello world ``` * The complete command that was executed act -r Any output from the command [bla/bla2] 🚀 Start image=node:12.6-buster-slim [bla/bla2] 🐳 docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[] [bla/bla2] ⭐ Run echo hello world | hello world [bla/bla2] ✅ Success - echo hello world Desired behaviour: The second time the command is run it should no run because no changes were made to docs/* files.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 21, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:764135625 --> @github-actions[bot] commented on GitHub (Jan 21, 2021): Issue is stale and will be closed in 14 days unless there is new activity
Author
Owner

@sloansparger commented on GitHub (Aug 12, 2021):

Having the same issue.

<!-- gh-comment-id:897786639 --> @sloansparger commented on GitHub (Aug 12, 2021): Having the same issue.
Author
Owner

@catthehacker commented on GitHub (Aug 17, 2021):

Leaving it open but I'm not sure if it's easy to implement so I won't treat it with priority

<!-- gh-comment-id:900335844 --> @catthehacker commented on GitHub (Aug 17, 2021): Leaving it open but I'm not sure if it's easy to implement so I won't treat it with priority
Author
Owner

@kneal commented on GitHub (Dec 7, 2023):

Was this validated to still be an issue after the work done in #1618?

<!-- gh-comment-id:1845872390 --> @kneal commented on GitHub (Dec 7, 2023): Was this validated to still be an issue after the work done in #1618?
Author
Owner

@ChristopherHX commented on GitHub (Dec 7, 2023):

Was this validated to still be an issue after the work done in #1618?

Yes, the filter is still not applied to the act cli. This code is in use in Gitea Actions.

<!-- gh-comment-id:1846192803 --> @ChristopherHX commented on GitHub (Dec 7, 2023): > Was this validated to still be an issue after the work done in #1618? Yes, the filter is still not applied to the act cli. This code is in use in Gitea Actions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#318
No description provided.