-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Can't get since_last_remote_commit
to work properly on pull_request event
#276
Comments
Thanks for reporting this issue. |
Can you try using the latest release: |
I have but I get the same results |
Can you add more information about the full workflow setup, also note that the |
steps:
- name: Checkout code
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Comprobar qué archivos han cambiado
id: changed-files
uses: tj-actions/changed-files@v11.8
with:
since_last_remote_commit: 'true'
- name: Dockerfile o requerimientos han cambiado
id: set-output
run: |
for file in ${{ steps.changed-files.outputs.modified_files }}; do
echo "$file was added"
done That the whole setup. |
What's the output from the logs ?? Ideally uploading the logs would be helpful. |
Sure,
|
It seems to me like its not comparing to the right commit |
From the logs seems this is triggered by a pull_request based event which uses the last commit on the base branch in this case main (latest commit/HEAD) -> PR branch (latest commit/HEAD) If you'll like to use the last remote commit on the same branch you can switch on:
pull_request:
branches:
- main TO on:
push:
branches:
- "**" # OR: Objetivo-6 |
But I want the action to only trigger on pull requests |
Which commit are you expecting to use ??
|
The last commit on the pull request branch |
* Fixed regression bug with base_sha for pull_request Fixes: #276 * Update action.yml * Update entrypoint.sh * Update entrypoint.sh * Update entrypoint.sh * Update entrypoint.sh
@Balrrach This should be resolved in the latest release. Thanks |
I can confirm the problem is solved. Thanks a lot for the fast answer! |
since_last_remote_commit
to work properly on pull_request eventsince_last_remote_commit
to work properly on pull_request event
since_last_remote_commit
to work properly on pull_request eventsince_last_remote_commit
to work properly on pull_request event
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
If I am not mistaken
since_last_remote_commit
option compares all changes between the last commit available in remote.When using the next step:
I get the following result:
README.md iv.yaml package.json
I am changing only the github action file between pushes, how is it possible?. What am I missing?.
Describe the solution you'd like?
Explanation of current behabior
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: