You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -62,6 +63,16 @@ The policy above is enforced by [branch protection](https://docs.github.com/repo
62
63
63
64
Code ownership is declared in [`.github/CODEOWNERS`](.github/CODEOWNERS) (`* @doherty100`), which automatically requests the owner as a reviewer on pull requests.
64
65
66
+
## Collaborator Access and Issue Assignment
67
+
68
+
**TL;DR — to assign someone an issue/PR, they need `triage` access (or higher); a past commit alone is not enough.**
69
+
70
+
- Issues/PRs can only be assigned to users with **write, triage, or admin** access — or anyone who has commented on that item.
71
+
- A prior commit / *Contributors* listing grants **no** permission; a `read`-only user won't appear in the assignee picker.
72
+
- Use **`triage`** for reviewers/triagers: it allows issue/PR management and assignment but **no commits or merges to any branch** (including `main`).
73
+
- Granting access (owner/admin only): invite the user at the `triage` level, then **verify the pending invitation's level** — an older unaccepted invitation at a higher level (e.g. `write`) is not auto-downgraded and must be patched down.
74
+
- The user must **accept the invitation** before access takes effect and they become assignable.
75
+
65
76
## Continuous Integration
66
77
67
78
Pull requests targeting `vnext` (and pushes to `vnext`) automatically run lightweight static-analysis checks via GitHub Actions. These do **not** deploy anything to Azure and require no credentials. The workflows live in [`.github/workflows/`](.github/workflows):
0 commit comments