Workspace authorization reads the workspace from the existing record, so a create (which has no record yet) is checked only at org level. Done when a create is authorized against the workspace it will land in.
Close reason
Source create is the only create taking a workspace from its body; it is now checked against that workspace. Other creates land in the default workspace, already covered at the route.
Imported from beads archie-core-ed8tw · GitHub #1639 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13
Workspace authorization reads the workspace from the existing record, so a create (which has no record yet) is checked only at org level. Done when a create is authorized against the workspace it will land in.
### Close reason
Source create is the only create taking a workspace from its body; it is now checked against that workspace. Other creates land in the default workspace, already covered at the route.
---
_Imported from beads `archie-core-ed8tw` · GitHub #1639 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13_
sam
added the mediumbug labels 2026-10-27 13:39:49 +00:00
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.
Workspace authorization reads the workspace from the existing record, so a create (which has no record yet) is checked only at org level. Done when a create is authorized against the workspace it will land in.
Close reason
Source create is the only create taking a workspace from its body; it is now checked against that workspace. Other creates land in the default workspace, already covered at the route.
Imported from beads
archie-core-ed8tw· GitHub #1639 · type bug · priority P2 · created 2026-10-11 · closed 2026-10-13