Skip to content

[CI] Improve mcpchecker pipeline to eval code changes from Pull Requests #832

@manusa

Description

@manusa

PR branch workflow runs should never rely on repo secrets (there's a workaround for this, but it SHOULD NEVER be used).

As a follow up, I think that what we need to do is improve the workflow_dispatch so that it runs the action from the main branch but executes the evals (and evaluated code) from the PR branch (an extra-level of carefulness should be required for those authorized to trigger the workflow in order to ensure that no secrets would be leaked by a maliciously crafted PR)

Originally posted by @manusa in #827 (comment)

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