feat(msgraph): add auth and client foundation#21408
Conversation
|
Thanks for splitting this out, and for taking the earlier review direction on #19815 seriously — the plugin + CLI + skill shape is exactly right. One thing that'll make these much easier to review: the 5 PRs are currently all based on Could you retarget them as a proper stack so diffs are incremental?
Planning to review bottom-up starting with this one. Thanks for working through the split. |
|
gh pr edit is failing with "branch not found" because the intermediate branches don't exist upstream. I don't have write access to push them. Could you advise on how to proceed? @teknium1 |
|
Merged via PR #21922. Your two commits ( Two small follow-ups added on top during salvage:
The remaining PRs in the stack (#21409–#21412) are still open and will be reviewed next against current |
References PR #19815.
This is the first part of the Microsoft Teams meeting pipeline stack, split out in response to maintainer review on the original PR.
This slice is intentionally scoped to:
The goal here is to keep the review surface small and establish the Graph auth/client layer before the webhook listener, pipeline runtime, outbound delivery, and docs follow-up PRs in the stack.
Review and merge in stack order.