@cesar-richard/git-connector-sdk 2.11.0 → 2.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/schema.d.ts +144 -5
  2. package/package.json +1 -1
package/dist/schema.d.ts CHANGED
@@ -256,7 +256,14 @@ export interface components {
256
256
  name: string | null;
257
257
  email: string | null;
258
258
  }[];
259
- /** @description True when the activity is open AND has at least one requested reviewer who has not yet responded. Always false for issues. */
259
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab and for issues). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts. A consumer deciding whether a PR is waiting on someone must read BOTH — a PR asked only of a team has an empty `requestedReviewers`. */
260
+ requestedTeams: {
261
+ slug: string;
262
+ name: string;
263
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
264
+ members: string[];
265
+ }[];
266
+ /** @description True when the activity is open AND a review is still awaited — from a named reviewer who has not responded, OR from a requested team. Always false for issues. */
260
267
  awaitingReview: boolean;
261
268
  reviewRequestedAt: string | null;
262
269
  /** @description Review lifecycle bucket, or null for issues — an issue is not under review, so no bucket applies. Pass ?viewer to split 'open-awaiting-my-review' from 'open-awaiting-other-review'; without it, a pending review always reads as 'open-awaiting-other-review'. */
@@ -304,7 +311,14 @@ export interface components {
304
311
  name: string | null;
305
312
  email: string | null;
306
313
  }[];
307
- /** @description True when the activity is open AND has at least one requested reviewer who has not yet responded. Always false for issues. */
314
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab and for issues). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts. A consumer deciding whether a PR is waiting on someone must read BOTH — a PR asked only of a team has an empty `requestedReviewers`. */
315
+ requestedTeams: {
316
+ slug: string;
317
+ name: string;
318
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
319
+ members: string[];
320
+ }[];
321
+ /** @description True when the activity is open AND a review is still awaited — from a named reviewer who has not responded, OR from a requested team. Always false for issues. */
308
322
  awaitingReview: boolean;
309
323
  reviewRequestedAt: string | null;
310
324
  /** @description Review lifecycle bucket, or null for issues — an issue is not under review, so no bucket applies. Pass ?viewer to split 'open-awaiting-my-review' from 'open-awaiting-other-review'; without it, a pending review always reads as 'open-awaiting-other-review'. */
@@ -490,6 +504,13 @@ export interface components {
490
504
  name: string | null;
491
505
  email: string | null;
492
506
  }[];
507
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
508
+ requestedTeams: {
509
+ slug: string;
510
+ name: string;
511
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
512
+ members: string[];
513
+ }[];
493
514
  updatedAt: string;
494
515
  mergedAt: string | null;
495
516
  reviewRequestedAt: string | null;
@@ -704,6 +725,13 @@ export interface components {
704
725
  name: string | null;
705
726
  email: string | null;
706
727
  }[];
728
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
729
+ requestedTeams: {
730
+ slug: string;
731
+ name: string;
732
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
733
+ members: string[];
734
+ }[];
707
735
  updatedAt: string;
708
736
  mergedAt: string | null;
709
737
  reviewRequestedAt: string | null;
@@ -1457,6 +1485,13 @@ export interface components {
1457
1485
  name: string | null;
1458
1486
  email: string | null;
1459
1487
  }[];
1488
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
1489
+ requestedTeams: {
1490
+ slug: string;
1491
+ name: string;
1492
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
1493
+ members: string[];
1494
+ }[];
1460
1495
  updatedAt: string;
1461
1496
  mergedAt: string | null;
1462
1497
  reviewRequestedAt: string | null;
@@ -1573,6 +1608,12 @@ export interface components {
1573
1608
  }[];
1574
1609
  };
1575
1610
  Provider: "github" | "gitlab";
1611
+ RequestedTeam: {
1612
+ slug: string;
1613
+ name: string;
1614
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
1615
+ members: string[];
1616
+ };
1576
1617
  ResolvedUser: {
1577
1618
  id: string;
1578
1619
  login: string;
@@ -1728,6 +1769,13 @@ export interface components {
1728
1769
  name: string | null;
1729
1770
  email: string | null;
1730
1771
  }[];
1772
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
1773
+ requestedTeams: {
1774
+ slug: string;
1775
+ name: string;
1776
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
1777
+ members: string[];
1778
+ }[];
1731
1779
  updatedAt: string;
1732
1780
  mergedAt: string | null;
1733
1781
  reviewRequestedAt: string | null;
@@ -1906,6 +1954,13 @@ export interface components {
1906
1954
  name: string | null;
1907
1955
  email: string | null;
1908
1956
  }[];
1957
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
1958
+ requestedTeams: {
1959
+ slug: string;
1960
+ name: string;
1961
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
1962
+ members: string[];
1963
+ }[];
1909
1964
  updatedAt: string;
1910
1965
  mergedAt: string | null;
1911
1966
  reviewRequestedAt: string | null;
@@ -2137,6 +2192,13 @@ export interface operations {
2137
2192
  name: string | null;
2138
2193
  email: string | null;
2139
2194
  }[];
2195
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
2196
+ requestedTeams: {
2197
+ slug: string;
2198
+ name: string;
2199
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
2200
+ members: string[];
2201
+ }[];
2140
2202
  updatedAt: string;
2141
2203
  mergedAt: string | null;
2142
2204
  reviewRequestedAt: string | null;
@@ -2319,6 +2381,13 @@ export interface operations {
2319
2381
  name: string | null;
2320
2382
  email: string | null;
2321
2383
  }[];
2384
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
2385
+ requestedTeams: {
2386
+ slug: string;
2387
+ name: string;
2388
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
2389
+ members: string[];
2390
+ }[];
2322
2391
  updatedAt: string;
2323
2392
  mergedAt: string | null;
2324
2393
  reviewRequestedAt: string | null;
@@ -2501,6 +2570,13 @@ export interface operations {
2501
2570
  name: string | null;
2502
2571
  email: string | null;
2503
2572
  }[];
2573
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
2574
+ requestedTeams: {
2575
+ slug: string;
2576
+ name: string;
2577
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
2578
+ members: string[];
2579
+ }[];
2504
2580
  updatedAt: string;
2505
2581
  mergedAt: string | null;
2506
2582
  reviewRequestedAt: string | null;
@@ -2739,6 +2815,13 @@ export interface operations {
2739
2815
  name: string | null;
2740
2816
  email: string | null;
2741
2817
  }[];
2818
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
2819
+ requestedTeams: {
2820
+ slug: string;
2821
+ name: string;
2822
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
2823
+ members: string[];
2824
+ }[];
2742
2825
  updatedAt: string;
2743
2826
  mergedAt: string | null;
2744
2827
  reviewRequestedAt: string | null;
@@ -2916,6 +2999,13 @@ export interface operations {
2916
2999
  name: string | null;
2917
3000
  email: string | null;
2918
3001
  }[];
3002
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
3003
+ requestedTeams: {
3004
+ slug: string;
3005
+ name: string;
3006
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
3007
+ members: string[];
3008
+ }[];
2919
3009
  updatedAt: string;
2920
3010
  mergedAt: string | null;
2921
3011
  reviewRequestedAt: string | null;
@@ -3093,6 +3183,13 @@ export interface operations {
3093
3183
  name: string | null;
3094
3184
  email: string | null;
3095
3185
  }[];
3186
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
3187
+ requestedTeams: {
3188
+ slug: string;
3189
+ name: string;
3190
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
3191
+ members: string[];
3192
+ }[];
3096
3193
  updatedAt: string;
3097
3194
  mergedAt: string | null;
3098
3195
  reviewRequestedAt: string | null;
@@ -4127,7 +4224,14 @@ export interface operations {
4127
4224
  name: string | null;
4128
4225
  email: string | null;
4129
4226
  }[];
4130
- /** @description True when the activity is open AND has at least one requested reviewer who has not yet responded. Always false for issues. */
4227
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab and for issues). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts. A consumer deciding whether a PR is waiting on someone must read BOTH — a PR asked only of a team has an empty `requestedReviewers`. */
4228
+ requestedTeams: {
4229
+ slug: string;
4230
+ name: string;
4231
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4232
+ members: string[];
4233
+ }[];
4234
+ /** @description True when the activity is open AND a review is still awaited — from a named reviewer who has not responded, OR from a requested team. Always false for issues. */
4131
4235
  awaitingReview: boolean;
4132
4236
  reviewRequestedAt: string | null;
4133
4237
  /** @description Review lifecycle bucket, or null for issues — an issue is not under review, so no bucket applies. Pass ?viewer to split 'open-awaiting-my-review' from 'open-awaiting-other-review'; without it, a pending review always reads as 'open-awaiting-other-review'. */
@@ -4176,7 +4280,14 @@ export interface operations {
4176
4280
  name: string | null;
4177
4281
  email: string | null;
4178
4282
  }[];
4179
- /** @description True when the activity is open AND has at least one requested reviewer who has not yet responded. Always false for issues. */
4283
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab and for issues). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts. A consumer deciding whether a PR is waiting on someone must read BOTH — a PR asked only of a team has an empty `requestedReviewers`. */
4284
+ requestedTeams: {
4285
+ slug: string;
4286
+ name: string;
4287
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4288
+ members: string[];
4289
+ }[];
4290
+ /** @description True when the activity is open AND a review is still awaited — from a named reviewer who has not responded, OR from a requested team. Always false for issues. */
4180
4291
  awaitingReview: boolean;
4181
4292
  reviewRequestedAt: string | null;
4182
4293
  /** @description Review lifecycle bucket, or null for issues — an issue is not under review, so no bucket applies. Pass ?viewer to split 'open-awaiting-my-review' from 'open-awaiting-other-review'; without it, a pending review always reads as 'open-awaiting-other-review'. */
@@ -4225,7 +4336,14 @@ export interface operations {
4225
4336
  name: string | null;
4226
4337
  email: string | null;
4227
4338
  }[];
4228
- /** @description True when the activity is open AND has at least one requested reviewer who has not yet responded. Always false for issues. */
4339
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab and for issues). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts. A consumer deciding whether a PR is waiting on someone must read BOTH — a PR asked only of a team has an empty `requestedReviewers`. */
4340
+ requestedTeams: {
4341
+ slug: string;
4342
+ name: string;
4343
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4344
+ members: string[];
4345
+ }[];
4346
+ /** @description True when the activity is open AND a review is still awaited — from a named reviewer who has not responded, OR from a requested team. Always false for issues. */
4229
4347
  awaitingReview: boolean;
4230
4348
  reviewRequestedAt: string | null;
4231
4349
  /** @description Review lifecycle bucket, or null for issues — an issue is not under review, so no bucket applies. Pass ?viewer to split 'open-awaiting-my-review' from 'open-awaiting-other-review'; without it, a pending review always reads as 'open-awaiting-other-review'. */
@@ -4380,6 +4498,13 @@ export interface operations {
4380
4498
  name: string | null;
4381
4499
  email: string | null;
4382
4500
  }[];
4501
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
4502
+ requestedTeams: {
4503
+ slug: string;
4504
+ name: string;
4505
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4506
+ members: string[];
4507
+ }[];
4383
4508
  updatedAt: string;
4384
4509
  mergedAt: string | null;
4385
4510
  reviewRequestedAt: string | null;
@@ -4595,6 +4720,13 @@ export interface operations {
4595
4720
  name: string | null;
4596
4721
  email: string | null;
4597
4722
  }[];
4723
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
4724
+ requestedTeams: {
4725
+ slug: string;
4726
+ name: string;
4727
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4728
+ members: string[];
4729
+ }[];
4598
4730
  updatedAt: string;
4599
4731
  mergedAt: string | null;
4600
4732
  reviewRequestedAt: string | null;
@@ -4810,6 +4942,13 @@ export interface operations {
4810
4942
  name: string | null;
4811
4943
  email: string | null;
4812
4944
  }[];
4945
+ /** @description Teams asked to review (GH `requested_teams`; always empty on GitLab, which has no such notion). Kept SEPARATE from `requestedReviewers` on purpose: 'you were asked' and 'your team was asked' are different facts, and folding members into the reviewer list would make that field lie about what the provider holds. A PR asked of a team only counts as awaiting review through this field. */
4946
+ requestedTeams: {
4947
+ slug: string;
4948
+ name: string;
4949
+ /** @description Logins of the team's members, resolved at sync time. EMPTY does not mean the team is empty: the token may lack `read:org`, or the team may have been renamed or removed. The team itself is what tells you the PR was addressed — treat missing members as unknown, never as nobody. */
4950
+ members: string[];
4951
+ }[];
4813
4952
  updatedAt: string;
4814
4953
  mergedAt: string | null;
4815
4954
  reviewRequestedAt: string | null;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cesar-richard/git-connector-sdk",
3
- "version": "2.11.0",
3
+ "version": "2.12.0",
4
4
  "description": "TypeScript SDK for the git-connector v1 API (work items + iterations aggregated from GitHub/GitLab). Version published on npm tracks server releases.",
5
5
  "license": "MIT",
6
6
  "repository": {