Skip to content
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

remove .github/workflows/no-response.yml #4471

Open
milahu opened this issue May 28, 2024 · 3 comments
Open

remove .github/workflows/no-response.yml #4471

milahu opened this issue May 28, 2024 · 3 comments

Comments

@milahu
Copy link

milahu commented May 28, 2024

this action always throws error in my fork of pyload

plus, auto-closing issues is stupid ...

@vuolter
Copy link
Contributor

vuolter commented May 28, 2024

Last time I checked this action was a while ago, so could you tell us more about what kind of issue you are experiencing in your fork?
Imho no-response works best for plugin requests and feedback awaiting (so label dependent), I agree that other cases are not the best to deal with.

@milahu
Copy link
Author

milahu commented May 28, 2024

i guess this fails because my fork has no issues page
but i found no such issue at lee-dohm/no-response

log from failed run

Run lee-dohm/[email protected]

/home/runner/work/_actions/lee-dohm/no-response/v0.5.0/dist/index.js:3430
        const error = new requestError.RequestError(message, status, {
                      ^

RequestError [HttpError]: Resource not accessible by integration
    at /home/runner/work/_actions/lee-dohm/no-response/v0.5.0/dist/index.js:3430:23
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  status: 403,
  headers: ...,
  request: {
    method: 'POST',
    url: 'https://api.github.com/repos/milahu/pyload/labels',
    headers: ...,
    body: '{"name":"feedback wanted","color":"ffffff"}',
    request: ...
  },
  documentation_url: 'https://docs.github.com/rest/issues/labels#create-a-label'
}

@milahu
Copy link
Author

milahu commented Jun 1, 2024

i guess this fails because my fork has no issues page

nope, still fails when i enable issues

this action is disabled in pyload/pyload/actions
but as soon as i fork the repo, it is enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants