Skip to content

bot:status command causes many responses - and doesn't allow addressing a single instance #363

@casparvl

Description

@casparvl

See e.g. EESSI/software-layer#1366 (comment)

the instance: argument is not respected, all instances monitoring this repo simply respond. For the status, I typically only need a single bot to provide me with an overview, all (should) produce the same overview anyway since all they do is analyze the comments from the PR (which should lead to the same result for all bots).

Admittedly, it's a nice to have. Might not be too hard to implement though, as we do similar filtering on the build command already.

This makes me think: the newly introduced scancel command: does that allow addressing a specific bot instance? Maybe that should even be enforced in order to avoid unintentionally cancelling jobs from multiple bot instances.

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