You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It works a expected by listing the newly added file name and reading when pull request is raised and pull request status is open .
But when pull request is merged It is not working as expected .
Output of github actions :
Run bash $GITHUB_ACTION_PATH/entrypoint.sh
changed-files
Resolving repository path...
Retrieving changes between 307[82](https://github.com/myrepo/access/runs/5415320264?check_suite_focus=true#step:3:82)7b1f6e70f1f2ceb[92](https://github.com/myrepo/access/runs/5415320264?check_suite_focus=true#step:3:92)646800[94](https://github.com/myrepo/access/runs/5415320264?check_suite_focus=true#step:3:94)ffd610535d (security_poc) → 307827b1f6e70f1f2ceb9264680094ffd610535d (test1)
Getting diff...
Input files pattern: accessRequest/2022-02-23-12:04:54-0800-access.json|accessRequest/acc.json
Added files:
Copied files:
Deleted files:
Modified files:
Renamed files:
Type Changed files:
Unmerged files:
Unknown files:
All changed and modified files:
All changed files:
All modified files:
I want it to work for all actions
pull_request:[opened, synchronize, edited, closed]
To Reproduce
use workflow which i am using .
create a pull request to any file in repo with extension .json.
Reading newly modified/added file name can be read.
but when the PR is merged unable to read the file name
Getting diff...
Input files pattern: accessRequest/2022-02-23-12:04:54-0800-access.json|accessRequest/acc.json
Added files:
Copied files:
Deleted files:
Modified files:
Renamed files:
Type Changed files:
Unmerged files:
Unknown files:
All changed and modified files:
All changed files:
All modified files:
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
Expecting to read the file name with extension **/*.json from pull request merge
Relevant log output
No response
Anything else?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@rajeshwer Given that the PR branch would already be merged into the target/base branch the last SHA on the base branch would be the modified PR changes that's why you don't see any files.
There are two ways around this:
1 Using the push event on the target branch to find all files that have changed since the last remote commit on the target branch.
...
- name: Get specific changed filesid: changed-files-specificuses: tj-actions/changed-files@v17.2with:
since_last_remote_commit: "true"files: | **/*.json
Using the first commit of the PR as the reference for performing change detection. (NB: This would mean that the changes made in the first commit wouldn't be compared to the target branch)
- name: Get specific changed filesid: changed-files-specificuses: tj-actions/changed-files@v17.2with:
base_sha: ${{ github.event.pull_request.base.sha }}files: | **/*.json
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
Hello
I am trying to get the name of the file added after pull request is merged
below is my work flow which i am currently using
It works a expected by listing the newly added file name and reading when pull request is raised and pull request status is open .
But when pull request is merged It is not working as expected .
Output of github actions :
I want it to work for all actions
pull_request:[opened, synchronize, edited, closed]
To Reproduce
use workflow which i am using .
create a pull request to any file in repo with extension .json.
Reading newly modified/added file name can be read.
but when the PR is merged unable to read the file name
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
Expecting to read the file name with extension **/*.json from pull request merge
Relevant log output
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: