Loosen the Forgejo trigger write-access gate #215
No reviewers
Labels
No labels
Agent
Ignore
Agent
In Progress
Agent
Planned
Agent
Planning
Agent
Ready
Agent
Triage
Compat
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lucas/omp-deck!215
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/issue-214-loosen-write-gate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes: #214
row.repo) and the issue/PR opener skip the permission check entirely (case-insensitive).DispatchApi.readRepoPrivate; on private repos areadauthor may trigger only conversation reasons on a non-PR issue whose mapped session (if any) is aforgejo_conversation. The visibility lookup runs last; any API failure drops the trigger.Note: the test "an opener without write access is dropped" (issue-title trigger) was removed. An issue-opened trigger's author is always the opener, so it is now allowed by design.
Tests:
bun test src/forgejo/dispatcher.test.tspasses (161 tests), including new exemption cases. Atscerror inbridge/session-policy.test.tsexisted before this change.