Skip to content

Automatic CI does not always work #1833

Description

@BridgeAR

At the moment our CI often replies with Sadly, an error occurred when I tried to trigger a build. :(. If I am correct the lite CI job is not triggered anymore.

There was definitely a recent update to the bot since it now updates the latest post with the latest CI run instead of posting new entries every time. I guess that is related?

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