1Password/onepassword-operator
1
0
Fork 0
mirror of https://github.com/1Password/onepassword-operator.git synced 2025-11-01 04:09:39 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
2a931cd782f2d31f0b239dd8111bf0b075ded7e0
onepassword-operator/docs/fork-pr-testing.md
Volodymyr Zotov 2a931cd782 Update fork-pr-testing doc
2025-10-28 11:14:56 -05:00

1.4 KiB
Raw Blame History

Fork PR Testing Guide

This document explains how testing works for external pull requests from forks.

Overview

The testing system consists of two main workflows:

  1. E2E Tests (test-e2e.yml) - Runs automatically for internal PRs, need manual trigger on external PRs.
  2. Ok To Test (ok-to-test.yml) - Dispatches repository_dispatch event when maintainer put's /ok-to-test sha=<commit hash> comment in the forked PR thread.

How It Works

1. PR is created by maintainer:

For the PR created by maintainer E2E Test workflow starts automatically. The PR check will reflect the status of the job.

2. PR is created by external contributor:

For the PR created by external contributor E2E Test workflow won't start automatically. Maintainer should make a sanity check of the changes and run it manually by:

  1. Putting a comment /ok-to-test sha=<latest commit hash> in the PR thread.
  2. E2E Test workflow starts.
  3. After E2E Test workflow finishes, the commit with a link and workflow status will appear in the thread.
  4. Maintainer can merge PR or request the changes based on the E2E Test results.

Notes

  • Only users with write permissions can trigger the /ok-to-test command.
  • External PRs are automatically detected and prevented from running e2e tests automatically.
  • Running e2e test on the external PR is optional. Maintainer can merge PR without running it. Maintainer decides whether it's needed to run an E2E test.