docs: document conservative PR smoke classification
This commit is contained in:
@@ -51,6 +51,6 @@ push to test after merge
|
||||
└── structured regression evidence upload
|
||||
```
|
||||
|
||||
Use one change workflow rather than separate branch and PR workflow files. It subscribes to non-default `push` plus `pull_request` `opened` and `reopened`, but not `synchronize`; later branch pushes are the single trigger. The classification job queries Gitea using the checkout credential held only in memory and requires both the open PR head branch and exact SHA to match. Never infer open state from retained pull-request refs. Cancel superseded change runs for the same branch and expose one required aggregate result.
|
||||
Use one change workflow rather than separate branch and PR workflow files. It subscribes to non-default `push` plus `pull_request` `opened` and `reopened`, but not `synchronize`; later branch pushes are the single trigger. The classification job compares the exact commit with Gitea pull-request head refs without exposing a broad API token to candidate-controlled code. Because Gitea retains those refs after closure, an unchanged closed-PR head may conservatively receive smoke again; a new branch-only commit receives repository validation only. Cancel superseded change runs for the same branch and expose one required aggregate result.
|
||||
|
||||
The integrated workflow runs only on `push` to `test` and queues instead of cancelling older integrated commits. It requires an explicit non-production base URL and runtime-only authentication when the regression set requires it. Its artifacts are integrated regression evidence, not a release-facing UAT verdict. `UAT_PASSED` additionally requires the project UAT procedure to verify the immutable Delivery deployment tuple live before and after the run. Smoke is not complete UAT, and full regression does not run on a PR.
|
||||
|
||||
Reference in New Issue
Block a user