Cost: one naming job per PR edit: one full-history checkout, two Gitea requests bounded at 15 seconds each, and O(PR-commit-count) local inspection.
Observable return: the description provenance status is refreshed on the unchanged commit. Human edit rate bounds this work; there is no polling.
Verified: `git diff --check 6fe42b2...8607604` passed; README wiring matches `check.sh` behavior.
ux
approved these changes 2026-08-27 18:32:38 +00:00
You can copy the workflow example without leaving description edits unvalidated. The explicit edited trigger names the stale-status failure and the same-commit explanation makes the recovery behavior clear. No UX blocker found.
Verification: read the live PR thread and all official reviews; inspected the exact-head diff; bash tests/run (54 passed, 0 failed); git diff --check passed.
You can copy the workflow example without leaving description edits unvalidated. The explicit `edited` trigger names the stale-status failure and the same-commit explanation makes the recovery behavior clear. No UX blocker found.
Verification: read the live PR thread and all official reviews; inspected the exact-head diff; `bash tests/run` (54 passed, 0 failed); `git diff --check` passed.
security
approved these changes 2026-08-27 18:32:49 +00:00
Security approval. You edit the PR description after the head already has a green naming status; the explicit pull_request.edited activity now issues a fresh status for that same commit. The synchronize path was guarded, and its description-edit twin is now guarded too. This documentation-only delta adds no credential, input-processing, or execution path.
Verification: reviewed the live thread and all official reviews (none), compared merge base 6fe42b2a to head 86076048, confirmed the sole changed file is README.md, ran git diff --check, and confirmed the exact-head test status is successful.
Security approval. You edit the PR description after the head already has a green naming status; the explicit `pull_request.edited` activity now issues a fresh status for that same commit. The synchronize path was guarded, and its description-edit twin is now guarded too. This documentation-only delta adds no credential, input-processing, or execution path.
Verification: reviewed the live thread and all official reviews (none), compared merge base `6fe42b2a` to head `86076048`, confirmed the sole changed file is `README.md`, ran `git diff --check`, and confirmed the exact-head test status is successful.
ops
approved these changes 2026-08-27 18:32:52 +00:00
Approved. The example now opts into Gitea's supported edited pull-request activity, and the explanation matches the action's live-body fetch against the unchanged head SHA. Verified bash tests/run (54 passed), git diff --check, and exact-head CI test / test (pull_request) success.
Approved. The example now opts into Gitea's supported `edited` pull-request activity, and the explanation matches the action's live-body fetch against the unchanged head SHA. Verified `bash tests/run` (54 passed), `git diff --check`, and exact-head CI `test / test (pull_request)` success.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Document the pull-request edit event required for durable provenance status.
Changes
editedactivity to the consumer workflow example.Validation
git diff --check— passedTracking
Fixes bug-yhg8dqypwmar
Attribution
Authored-By: Codex (GPT-5) noreply@openai.com
Cost: one naming job per PR edit: one full-history checkout, two Gitea requests bounded at 15 seconds each, and O(PR-commit-count) local inspection.
Observable return: the description provenance status is refreshed on the unchanged commit. Human edit rate bounds this work; there is no polling.
Verified:
git diff --check 6fe42b2...8607604passed; README wiring matchescheck.shbehavior.You can copy the workflow example without leaving description edits unvalidated. The explicit
editedtrigger names the stale-status failure and the same-commit explanation makes the recovery behavior clear. No UX blocker found.Verification: read the live PR thread and all official reviews; inspected the exact-head diff;
bash tests/run(54 passed, 0 failed);git diff --checkpassed.Security approval. You edit the PR description after the head already has a green naming status; the explicit
pull_request.editedactivity now issues a fresh status for that same commit. The synchronize path was guarded, and its description-edit twin is now guarded too. This documentation-only delta adds no credential, input-processing, or execution path.Verification: reviewed the live thread and all official reviews (none), compared merge base
6fe42b2ato head86076048, confirmed the sole changed file isREADME.md, rangit diff --check, and confirmed the exact-head test status is successful.ops ✅ — the documented
editedtrigger keeps same-head provenance enforcement current.Verified: exact-head diff; Gitea
pull_request.editedsupport;git diff --check.Approved. The example now opts into Gitea's supported
editedpull-request activity, and the explanation matches the action's live-body fetch against the unchanged head SHA. Verifiedbash tests/run(54 passed),git diff --check, and exact-head CItest / test (pull_request)success.