Zeshan Amjad
08/06/2025, 3:35 PMPylon
08/06/2025, 3:36 PMgt feedback --with-debug-context <any message>Pylon
08/06/2025, 3:55 PMZeshan Amjad
08/08/2025, 10:02 AMPylon
08/08/2025, 12:36 PMZeshan Amjad
08/08/2025, 12:41 PMPylon
08/08/2025, 5:27 PMFrank Harvey
08/08/2025, 5:58 PM["Lint Common","Lint Platform","SQLC Check","Test Common","Test Platform"]
I confirmed this is the same list the PR page (which you can see) has the same checks.
When CI finally showed as "passing", we see this (apologies for the verbosity, but I though that better than hand-waviness):
{
"ciRollup": "FAILING_NON_REQUIRED",
"statusChecks": [
{
"conclusion": "SUCCESS",
"completedAt": "2025-08-06T14:40:57.000Z",
"annotationCount": 0,
"workflow": {
"name": "Encore Test",
"id": 16780130353
},
"appName": "GitHub Actions",
"name": "Setup",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SUCCESS",
"completedAt": "2025-08-06T14:40:10.000Z",
"annotationCount": 0,
"workflow": {
"name": "Lint",
"id": 16780130334
},
"appName": "GitHub Actions",
"name": "Setup",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SKIPPED",
"completedAt": "2025-08-06T14:40:57.000Z",
"annotationCount": 0,
"workflow": {
"name": "Encore Test",
"id": 16780130353
},
"appName": "GitHub Actions",
"name": "Test Platform",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SKIPPED",
"completedAt": "2025-08-06T14:40:10.000Z",
"annotationCount": 0,
"workflow": {
"name": "Lint",
"id": 16780130334
},
"appName": "GitHub Actions",
"name": "Lint Common",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SKIPPED",
"completedAt": "2025-08-06T14:40:10.000Z",
"annotationCount": 0,
"workflow": {
"name": "Lint",
"id": 16780130334
},
"appName": "GitHub Actions",
"name": "Test Common",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SKIPPED",
"completedAt": "2025-08-06T14:40:10.000Z",
"annotationCount": 0,
"workflow": {
"name": "Lint",
"id": 16780130334
},
"appName": "GitHub Actions",
"name": "Lint Platform",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SUCCESS",
"completedAt": "2025-08-06T14:40:54.000Z",
"annotationCount": 0,
"workflow": {
"name": "Lint",
"id": 16780130334
},
"appName": "GitHub Actions",
"name": "SQLC Check",
"ciStatus": "COMPLETED"
},
{
"conclusion": "FAILURE",
"completedAt": "2025-08-06T14:40:51.000Z",
"annotationCount": 0,
"appName": "encoredev",
"name": "Encore Build ā wearegradient",
"ciStatus": "COMPLETED"
},
{
"conclusion": "SUCCESS",
"completedAt": "2025-08-06T14:39:33.000Z",
"annotationCount": 0,
"appName": "Graphite App",
"name": "Graphite / mergeability_check",
"ciStatus": "COMPLETED"
}
],
"commitSha": "6112adce11c665029de00e1d3f0c1970bc684126",
"ciStatus": {
"failingOptionalList": [
"Encore Build ā wearegradient"
],
"failingRequired": 0,
"failingOptional": 1,
"failingBaseRequired": 0,
"status": "COMPLETED"
}
}
the summary of which is:
1. encore build failed, but its not required
2. Encore Test / Test Platform skipped
3. Lint platform also skipped
So 2 of your required status checks reported "skipped" to us, so our merge queue said, "ok sounds good everything else is passing so I will merge this"
I'm not sure why it skipped, or why its now failing. Without knowing your CI config I can't really tell you. But in general, you can safely only run CI on branches prefixed with gtmq_ when the pull request opens, but not on push.
> We trust you with these permissions because we assume that the Graphite app will function as intended and not merge broken changes.
Agreed with this completely and a core requirement of our merge queue is correctness, and bugs definitely happen, but in this case I'm not sure what the correct answer is to allow us to prevent a broken mergeFrank Harvey
08/08/2025, 5:59 PMZeshan Amjad
08/11/2025, 10:09 AMgtmq_ branch, but by then it's too late
We've solved this by always running CI if startsWith(github.event.pull_request.head.ref, 'gtmq_') is true.
ā¤ļø Thanks for all of your help!
š It might be worth adding this to the Graphite merge queue documentation as something to avoid.