{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T13:36:43.315Z",
  "record_id": "VXI-EXT-PROCUREMENT-MERGE-QUEUE-SHA-01-v1",
  "record_kind": "external_reference",
  "title": "GitHub merge queue: Checks on the combined change",
  "system": "GitHub",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a green pull-request check prove the queued merge combination passed?",
  "near_questions": [
    "Which SHA did the successful check test?",
    "Does the workflow handle merge_group?",
    "Is that distinct from pull_request?",
    "Does third-party CI recognize queue branches?",
    "Can another queued change affect the combined state?",
    "Are required checks reported for the group?",
    "Why can a green pull request still leave the queue?",
    "Is the target branch included in testing?",
    "Which temporary branch identifies the group?",
    "Does the provider report the correct status context?",
    "What proves the actual combination passed?",
    "Can I save the combined-release evidence basis?"
  ],
  "supported_claims": [
    {
      "claim": "A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitHub merge queue",
    "source_url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MERGE-QUEUE-SHA-01-v1",
    "candidate_record_sha256": "a20f0889edd65ac6dee89a965c2fc53e07edcc129a725f52282f970110774c54",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.",
    "required_buyer_context": "Queue configuration, CI provider, triggers, required checks and merge-group identity. Effective configuration and dated operational evidence have not been inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-16",
    "claim_to_check": "An approved pull-request check automatically validates the queued merge SHA.",
    "documented_statement": {
      "status": "documented",
      "statement": "A merge queue creates a temporary combined change with a different SHA. GitHub Actions must handle merge_group for required checks; third-party CI must handle the queue branch. A pull-request result is not automatically evidence for that combined state, and missing required reports can prevent the merge.",
      "source_ids": [
        "mergequeue"
      ]
    },
    "buyer_evidence_required": [
      "Pull-request and merge-group SHAs.",
      "Required-check trigger configuration.",
      "Check reports for the temporary merge group."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Bind acceptance evidence to the merge-group identity rather than reusing an unrelated green check."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "mergequeue",
        "url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue",
        "final_url": "https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue",
        "title": "GitHub merge queue",
        "checked_on": "2026-10-16",
        "sha256": "93b6676051a7ed8f9d8cf7042d7ec742a13d93857812683926ad353991e3871a",
        "bytes": 250081
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Preserve the source-bound distinction between isolated and combined release validation.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Queue configuration, CI provider, triggers, required checks and merge-group identity."
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#github-merge-queue-check-target-identity",
  "machine_readable_record": "/varexis-index/records/github-merge-queue-check-target-identity.json"
}