Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes not detected on a manual trigger (workflow_dispatch) #235

Open
TuuZzee opened this issue Apr 22, 2024 · 5 comments
Open

Changes not detected on a manual trigger (workflow_dispatch) #235

TuuZzee opened this issue Apr 22, 2024 · 5 comments

Comments

@TuuZzee
Copy link

TuuZzee commented Apr 22, 2024

First of thanks for this action it's pretty neat!

I am using it on couple of my Github action workflow but I have one that can be trigger manually on any branch that doesn't seem to work as expected.
For some reasons the changes aren't detected, I am guessing I have configure this wrong but I am not sure where.
It's also giving me the warning: 'before' field is missing in event payload - changes will be detected from last commit
I have tried couple solution from other issues I found here but without success so far:

I have currently it set as such:

//...
on:
  workflow_dispatch:
//...

  checks:
//...
      - uses: dorny/paths-filter@v3
        id: filter
        with:
          base: ${{ github.ref }}
          filters: |
@darkxeno
Copy link

same issue here @dorny, the log show "changes will be detected from last commit" but every file is detected as a change.

@HuiNextSense
Copy link

HuiNextSense commented Aug 2, 2024

Same for me. It seems the ref can't be found so all the commits are included for the change detection.

@Matrix4348
Copy link

Matrix4348 commented Aug 29, 2024

Hello,

I came here because I was facing the same issue. However, the solution suggested in #158 helped me solve it; absence of changes is now properly acknowledged on manual triggering.

Edit: My bad, the problem is still there. The solution above might have only worked out of luck.

@melyux
Copy link

melyux commented Nov 1, 2024

This breaks all of our workflows that can also be run manually.

@dorny Looks like a bug with PR #53?

@silviorp
Copy link

silviorp commented Dec 5, 2024

I was having the same problem described in the OP and this workaround worked for me!
#201

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants