Conversation
✅ knip — no dead codeNo unused files, exports, types, or dependencies detected. |
iamfj
force-pushed
the
issue-142
branch
2 times, most recently
from
July 4, 2026 16:49
244c552 to
706d88c
Compare
Add `teams create`, `teams update`, `teams members`, `teams add-member`, and `teams remove-member` subcommands with resolver-backed team/user ID resolution and paginated membership fetching. Estimation, cycle, and triage settings are exposed as explicit true|false flags. Boolean flags accept only true|false (not 1/0/yes/no) so scripts can set or unset settings unambiguously, and numeric flags reject blank input, which Number() would otherwise coerce to 0. Closes #142
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds team management to the
teamscommand group:create,update,members,add-member, andremove-membersubcommands. Team/user IDs are resolved once in the command layer, and membership listing paginates so all members are fetched regardless of team size. Estimation, cycle, and triage settings are exposed as explicittrue|falseflags so scripts can set or unset them unambiguously. New GraphQL mutations (CreateTeam,UpdateTeam,AddTeamMember,RemoveTeamMember) and aGetTeamMembershipsquery back the service layer, with unit, command, and integration test coverage.Closes #142
Type of change
Checklist
npm run check:cipasses (lint + format)npx tsc --noEmitpasses (type check)npm testpasses (unit tests)Testing
npm run check:ci,npx tsc --noEmit, andnpm test(884 tests) all pass locally.Notes for reviewers
remove-memberresolves the membership id from the team + user pair by paginating memberships, since Linear deletes memberships by their own id.