Comments (2)
I'm having a similar problem. The action works perfectly fine in PRs/branches, but once I perform a merge operation... it fails because of the same problem.
I'm considering doing something similar as to what you have done, although perhaps even more complicated, with some added conditional logic to only perform the checkout when there is a merge operation (what remains to be seen is how I'll make it to define base
conditionally, as it doesn't make sense to obtain PREV_COMMIT_SHA
if I didn't perform a checkout yet).
Another option is to make this to not execute this action on merge, and modify the conditionals that depend on this one to also execute on merge. That would save less time in CI, but I don't expect as many merge operations as commits to PRs.
EDIT: It seems that we can use conditionals in expressions actions/runner#409 , the approximation is a bit brittle ("same" as in POSIX shell, ugh), but better than nothing.
from paths-filter.
Hi both.
Can't you achieve this with just base: ${{ github.ref }}
? It seems that its working correctly for both open PRs and further pushes to the PR and when I merge the PR to main
. Curious if I'm missing anything.
from paths-filter.
Related Issues (20)
- Override option to set all Filters to true HOT 2
- Changed files with git commands detects too many files
- Is it possible to check if a single folder has changed? HOT 2
- filter in folder changes does not seem to work HOT 1
- Error: Unable to locate executable file: git HOT 4
- Scheduled build always running even if no change in filter path HOT 4
- Node.js 16 actions are deprecated HOT 7
- Update major version tags to point to latest minor version commit when released HOT 2
- How to add individual files to this filter? HOT 1
- Create v3 short tag pointing at the latest v3 release HOT 1
- Working directory does not provide changes paths relative to it. HOT 1
- VSCode "Context Access might be invalid" warning HOT 2
- fix: Unexpected input(s) 'predicate-quantifier'
- Files changed in a PR are too many to be fully detected by dorny/paths-filter HOT 2
- [Help Wanted] Multiple negations in a file path of filters is not working as expected HOT 1
- Allow `pull_request_review` event.
- Changes not detected on a manual trigger (workflow_dispatch) HOT 1
- Comparison betwwen different tags not working where as it compares with default branch HOT 4
- Filter paths
- Force Push Unexpected Behavior
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from paths-filter.