Skip to content

Avoid logging errors when branches are already deleted #253

@bluekeyes

Description

@bluekeyes

Now that GitHub supports deleting branches on merge, Bulldozer frequently gets a 422 error response when trying to delete a ref. We should suppress these in the logs to avoid confusion, since there's no real problem.

This probably isn't necessary if we end up merging #243.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions