[PR #17756] Port ServicingPipeline.ps1 to ProjectsV2 #31356

Open
opened 2026-01-31 09:46:45 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/17756

State: closed
Merged: Yes


GraphQL was a steep learning curve, but I think I get it now. I've written the queries to go deep into objects to find the exact merge commit (for a PR) or the PR->merge commit chain (for an issue). This means that ServicingPipeline now supports issues in project boards rather than just pull requests!

One of the big benefits of doing it this way is that we no longer have to search all git commits for ones that match our pull request title format! Instead, we can just get the commit object ID directly from the graph and ask git to sort them in the right order.

I am sure that it is going to break.

**Original Pull Request:** https://github.com/microsoft/terminal/pull/17756 **State:** closed **Merged:** Yes --- GraphQL was a steep learning curve, but I think I get it now. I've written the queries to go deep into objects to find the exact merge commit (for a PR) or the PR->merge commit chain (for an issue). This means that ServicingPipeline now supports *issues* in project boards rather than just pull requests! One of the big benefits of doing it this way is that we no longer have to search all git commits for ones that match our pull request title format! Instead, we can just get the commit object ID directly from the graph and ask git to sort them in the right order. I am sure that it is going to break.
claunia added the pull-request label 2026-01-31 09:46:45 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#31356