Fix #361: team subject picker #368
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!368
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-361"
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?
Fixes #361 (survey #349 candidate 4): team-subject bindings are discoverable from the Access tab.
client.orgs.teams.list, one cached GET); picking a team composesteam:org/sluginto the subject field. 404/403/empty degrade to the text-only form, so non-org owners see no change.web/src/lib/access.js, charset mirrors ofidentity.ValidOrg/ValidSlug) with a friendly note — the server still revalidates on PUT.web/test/unit/access-subject.test.js(12 tests: picker/compose/validate + Access.jsx wiring guards); full web suite 712/712 green (3 smoke tests need a live non-setup server — the :8080 instance here answers 503 setup-only, pre-existing/environmental); vite + esbuild build clean.docs/features/01_identity_permissions.mdDecisions.