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-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ It gives org admins a place to manage CLA text and signing history, and gives co
9
9
- If a contributor has signed a non-current CLA version, they must re-sign before being considered compliant.
10
10
- Contributor compliance status is evaluated per org using the contributor's latest signed version for that org.
11
11
- 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.
12
+
- After a contributor signs/re-signs the latest CLA, the bot updates their open PR CLA checks back to success and removes stale CLA prompt comments.
12
13
- GitHub is the user-management source of truth for the app.
13
14
- The app has no local signup/password user-management system; DB user rows are GitHub-linked identity mirrors only.
14
15
- Authentication/session management is stateless JWT-based (HTTP-only cookie + signed JWT with `jti`).
@@ -158,8 +159,8 @@ This section amends your scenario list and adds missing scenarios.
158
159
### 6) Contributor signs/re-signs CLA
159
160
160
161
- Signature is stored with org, user, full CLA hash, accepted hash, assent metadata, immutable GitHub ID at signing time, timestamp, email provenance, and session evidence fields.
161
-
-For linked PR context (`repo` + `pr`), failing CLA check/comment can be updated to success/signed status.
162
-
-Current behavior note: updates are scoped to known PR context, not guaranteed bulk update of all open PRs for that contributor.
162
+
-If `repo` + `pr` is provided, the signer must match that PR author before targeted PR sync is applied.
163
+
-After signing/re-signing, open PRs authored by that contributor in the org are auto-synced: the latest CLA check run is updated to success and stale CLA prompt comments are deleted.
163
164
164
165
### 7) Signed CLA versions cannot be deleted
165
166
@@ -222,7 +223,7 @@ This section amends your scenario list and adds missing scenarios.
222
223
- Signed current CLA: passing check, no CLA comment.
- 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.
225
-
- After signing/re-signing, check/comment can auto-update for the target PR context.
226
+
- After signing/re-signing, CLA checks on signer-authored open PRs are auto-updated to success and stale CLA prompt comments are removed.
226
227
- Repository maintainers must require `CLA Bot / Contributor License Agreement` in GitHub branch protection/rulesets for merge blocking to be enforced.
0 commit comments