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
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ It gives org admins a place to manage CLA text and signing history, and gives co
11
11
- Admins can define an org-scoped bypass list of GitHub accounts that should always receive a passing CLA check.
12
12
- If a contributor has open pull requests and their signature becomes outdated after a CLA update, checks may need to be re-opened/re-evaluated and set to failing until re-signing is completed.
13
13
- After a contributor signs/re-signs the latest CLA, the app schedules an async workflow that updates their open PR CLA checks to success and removes stale CLA prompt comments.
14
+
- When an org is activated/deactivated, the app schedules an async workflow to re-check open PRs for that org so checks converge to the new enforcement mode.
14
15
- GitHub is the user-management source of truth for the app.
15
16
- The app has no local signup/password user-management system; DB user rows are GitHub-linked identity mirrors only.
16
17
- Authentication/session management is stateless JWT-based (HTTP-only cookie + signed JWT with `jti`).
@@ -179,7 +180,8 @@ This section amends your scenario list and adds missing scenarios.
- Org deactivated/uninstalled: signing blocked; webhook events set passing CLA checks and remove managed CLA prompts so PRs are not blocked by CLA while inactive.
184
+
- Activating or deactivating an org schedules an async open-PR recheck workflow so existing PR checks/comments converge automatically.
183
185
- Updating bypass list schedules async open-PR recheck so existing PRs converge to the latest policy.
184
186
-`/recheck` authorization: allowed for PR author, org member, or maintainer; unauthorized users are blocked.
185
187
- OAuth and install redirects sanitize `returnTo` to prevent open redirects.
@@ -230,6 +232,7 @@ This section amends your scenario list and adds missing scenarios.
- When CLA text changes, contributors on older signatures are marked as requiring re-sign; open PRs may require check re-evaluation and failure until re-signing.
232
234
- After signing/re-signing, an async workflow updates signer-authored open PR CLA checks to success and removes stale CLA prompt comments.
- CLA bot comment updates/deletions are restricted to CLA-managed comments tagged with an internal signature marker, preventing edits to third-party bot comments.
234
237
- Repository maintainers must require `CLA Bot / Contributor License Agreement` in GitHub branch protection/rulesets for merge blocking to be enforced.
235
238
- Markdown ordered lists preserve explicit authored numbering (for example `1.`, `2.`, `7.` stays `1, 2, 7`), and legal alpha markers (`a.` / `a)`) render as ordered sub-clauses with indentation.
0 commit comments