Run: error not found

[mainrs]

I wanted to setup the action on my repository but it fails running: https://github.com/mainrs/git-cm/pull/33/checks?check_run_id=898404696

The console says:

Run kentaro-m/auto-assign-action@v1.1.1
  with:
    repo-token: ***
    configuration-path: .github/auto_assign.yml
##[error]Not Found

[davegreenwp]

We're getting this in our workflow, but it's not clear what is not found, presuming this error relates to the file declared in configuration-path @kentaro-m ?

[kenny-alvizuris-cko]

I'm having the same issue when trying to run this action, the error does not specify what actually is not found any ideas?

[manubla4]

Im having the same issue here

[umihico]

In my case, I tried to dynamically generate my config file and failed. I found out this action fetch the file from remote. I guess this is intentional, because users can skip checkout (which is slow and heavy sometimes)

auto-assign-action/src/run.ts

Line 15 in 908f7e9

const config = await utils.fetchConfigurationFile(client, {

auto-assign-action/src/utils.ts

Line 107 in 908f7e9

export async function fetchConfigurationFile(client: github.GitHub, options) {

[katfir]

I have similar problem. I have workflow nested in one repo and it works with default config.
But workflows that calls it from another, crashes:

Run kentaro-m/auto-assign-action@v1.2.5
  with:
    configuration-path: .github/auto_assign.yml
    repo-token: ***
Error: Not Found

.github/auto_assign.yml is located in the same repo as reusable workflow. And workflow works in this repo by open pr trigger for example

[GregoryNative]

@kentaro-m any updates?

[davidmajercak]

I finally got something to work. As umihico said above, it is trying to pull the yml config from the remote.

I was trying to generate the yml config dynamically, but since it only existed locally, the config was never found. Had to settle for the less elegant solution of hard-coding a yml config for each team, and using a powershell script to find out which team the author belongs to, and then returning the filepath to that config.

You'll also need to use the checkout action as a first step.