search

trilom / file-changes-action

This action can be added, and you will get outputs of all of the files that have changed in your repository for you to use.
MIT License
167 stars 48 forks source link

Received event from pull_request, but also received a before or after #97

Closed ThiefMaster closed 4 years ago

ThiefMaster commented 4 years ago

I'm getting this warning:

Run trilom/file-changes-action@v1.2.3
##[warning]Received event from pull_request, but also received a before(f35bae5ca5b40913c37cbf26692edcca97bdab5b) or after(8899fae77545c573fdf69edac81b8c14258c010f) value.
I am assuming you want to use a Push event but forgot something, so I'm giving you a message.

This is just a normal run for a pull request I just updated (tried both with normal and forcee push). The before/after are old/new head of the PR's branch.

I do not care about individual commit. All I want is the list of files changed in the PR (ie between the base branch and the new head). Is this possible with this action? Or am I misunderstanding how it works?

ravikp7 commented 4 years ago

This action was working fine for me for the last 2 weeks to get the file changes on pull_request. Suddenly, today I'm now seeing this error and my workflow is broken. I'm not sure what's the issue, any help would be highly appreciated.

Below is the full error log:

##[warning]Received event from pull_request, but also received a before(7c7ef0090f3a708873ad344ba4dbafcff64fee06) or after(f1b15cebe90fa10a085b91b1c6b4df9f96e45c36) value.
 I am assuming you want to use a Push event but forgot something, so I'm giving you a message.
(node:3127) UnhandledPromiseRejectionWarning: Error: {"error":"500/TypeError","from":"sortChangedFiles","message":"There was an issue sorting files changed.","payload":"{}"}
    at run (/home/runner/work/_actions/trilom/file-changes-action/v1.2.3/dist/index.js:1:19989)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:3127) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:3127) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
##[error]There was an issue sorting changed files from Github.
Exception: {
  "error": "500/TypeError",
  "from": "sortChangedFiles",
  "message": "There was an issue sorting files changed.",
  "payload": "{}"
}
trilom commented 4 years ago

This should be resolved in #99

mrchief commented 4 years ago

Is this released yet? I'm on 1.2.4 and still see this warning.

electriquo commented 3 years ago

Is this released yet? I'm on 1.2.4 and still see this warning.

It has been a long time since the question was asked and the issue still persists. Is this project been abandoned?

@trilom on your spare time, could you kindly double check?