Skip to content

Archive plugin returns 404 and break when repo doesn't exist #879

@decyjphr

Description

@decyjphr

Problem Description

Archive plugin returns 404 and break when repo doesn't exist

What is actually happening

The logic expects the repo to exist (which makes sense in most cases) but sometimes the yaml might be creating new repo with the archived: false

What is the expected behavior

It should ignore 404 and continue handling other plugins

Error output, if available

Context

Are you using the hosted instance of probot/settings or running your own?

If running your own instance, are you using it with github.com or GitHub Enterprise?

Version of probot/settings

Version of GitHub Enterprise

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions