Problem Description

Currently, only repository collaborators with write access can trigger E2E tests on pull requests. This limitation prevents members of the openshift-pipelines organization from being able to easily test their changes via E2E workflows on their own pull requests, even if they are members of the organization.

Current Behavior

E2E tests can only be initiated by a limited set of users, specifically those with repository write permissions or trusted bots. Organization members who do not have direct write access to the repository are unable to trigger these crucial tests on their pull requests.

Expected Behavior

We should enable members of the openshift-pipelines organization to trigger E2E tests on their pull requests. This would allow for broader participation in testing and validation of contributions without requiring direct write access to the repository. Additionally, it would be beneficial to ensure that automated bots like renovate[bot] are recognized and trusted to trigger workflows.

Additional Context

This change aims to streamline the contribution and testing process for organization members, fostering a more collaborative environment and ensuring that changes are adequately tested before merging. It specifically addresses the scenario where organization members want to validate their work through E2E testing without needing explicit repository write permissions.