1Password/onepassword-operator
1
0
Fork 0
mirror of https://github.com/1Password/onepassword-operator.git synced 2025-10-22 07:28:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update documentation

Browse Source
This commit is contained in:
Volodymyr Zotov
2025-10-02 15:34:51 -05:00
parent d30ed0b9d7
commit d403a29fdc
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/fork-pr-testing.md
View File

@@ -6,7 +6,7 @@ This document explains how to test external pull requests using the dispatch act
The testing system consists of three main workflows: The testing system consists of three main workflows:
1. **E2E Tests [triggered by maintainer]** (`test-e2e.yml`) - Runs automatically for internal PRs, requires approval for external PRs 1. **E2E Tests** (`test-e2e.yml`) - Runs automatically for internal PRs, requires approval for external PRs
2. **Ok To Test** (`ok-to-test.yml`) - Processes slash commands to trigger fork testing 2. **Ok To Test** (`ok-to-test.yml`) - Processes slash commands to trigger fork testing
3. **E2E tests [fork]** (`test-e2e-fork.yml`) - Triggered manually via slash commands for external PRs 3. **E2E tests [fork]** (`test-e2e-fork.yml`) - Triggered manually via slash commands for external PRs
@@ -53,18 +53,18 @@ Once the initial checks have run (and failed), maintainers can test the PR using
4. **Workflow Execution** 4. **Workflow Execution**
The fork workflow runs two jobs: The fork workflow runs two jobs:
**a) `e2e-tests` job** (conditional) **a) `run-e2e-tests` job** (conditional)
- Only runs if: - Only runs if:
- Event is `repository_dispatch` - Event is `repository_dispatch`
- SHA parameter is not empty - SHA parameter is not empty
- PR head SHA contains the provided SHA - PR head SHA contains the provided SHA
- Calls the reusable `e2e-tests.yml` workflow - Calls the reusable `run-e2e-tests.yml` workflow
- Runs the actual E2E tests if conditions are met - Runs the actual E2E tests if conditions are met
**b) `update-check-status` job** (conditional) **b) `update-check-status` job** (conditional)
- Runs after `e2e-tests` completes - Runs after `e2e-tests` completes
- Updates the existing check for job named "e2e-tests" - Updates the existing check for job named "run-e2e-tests" from 'test-e2e.yml' workflow
- Sets the conclusion based on `e2e-tests` result: - Sets the conclusion based on `run-e2e-tests` result:
- ✅ **Success** if tests pass - ✅ **Success** if tests pass
- ❌ **Failure** if tests fail - ❌ **Failure** if tests fail
@@ -96,7 +96,7 @@ Once the initial checks have run (and failed), maintainers can test the PR using
## Workflow Files ## Workflow Files
- **`.github/workflows/ok-to-test.yml`** - Ok To Test - Slash command processor - **`.github/workflows/ok-to-test.yml`** - Ok To Test - Slash command processor
- **`.github/workflows/test-e2e.yml`** - E2E Tests [triggered by maintainer] - Initial PR checks - **`.github/workflows/test-e2e.yml`** - E2E Tests - Initial PR checks
- **`.github/workflows/test-e2e-fork.yml`** - E2E tests [fork] - Dispatch action handler - **`.github/workflows/test-e2e-fork.yml`** - E2E tests [fork] - Dispatch action handler
- **`.github/workflows/e2e-tests.yml`** - E2E Tests [reusable] - Reusable workflow for actual testing - **`.github/workflows/e2e-tests.yml`** - E2E Tests [reusable] - Reusable workflow for actual testing