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
If "depends on" or "blocked by" value isn't set in the body the check is failing on 404
RequestError [HttpError]: Not Found
at /home/runner/work/_actions/gregsdennis/dependencies-action/main/node_modules/@octokit/request/dist-node/index.js:66:23
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async run (/home/runner/work/_actions/gregsdennis/dependencies-action/main/index.js:78:39) {
status: 404,
Commit example
Expected behaviour is if the body is empty or no string match the check should pass through or have a custom flag to ignore 404 responses
The text was updated successfully, but these errors were encountered:
@Sashasugar I don't think the reasoning is right. There wouldn't be a 404 because the body is empty.
A 404 might result from the PR not existing, and I don't see how that can happen since the workflow should trigger from a PR creation or change. You'd get a different error if the body was missing.
If "depends on" or "blocked by" value isn't set in the body the check is failing on 404
Commit example
Expected behaviour is if the body is empty or no string match the check should pass through or have a custom flag to ignore 404 responses
The text was updated successfully, but these errors were encountered: