Skip to content

Add GitHub merge queue data workflow#37357

Draft
arshahTT wants to merge 7 commits intomainfrom
ashah-merge-queue-data
Draft

Add GitHub merge queue data workflow#37357
arshahTT wants to merge 7 commits intomainfrom
ashah-merge-queue-data

Conversation

@arshahTT
Copy link
Contributor

@arshahTT arshahTT commented Feb 8, 2026

Ticket

N/A - internal data pipeline work

Problem description

We need periodic merge queue visibility for tt-metal. GitHub does not expose a public merge queue API, and earlier approaches relied on non public endpoints that are not stable or reliable.

What changed

This PR introduces an internal GitHub Actions workflow that:

  • Uses only public GitHub APIs
  • Collects merge queue related data from:
    • Pull Requests API
    • PR head commit SHA
  • Generates a normalized snapshot representing merge readiness
  • Uploads the snapshot through the existing SFTP ingestion mechanism

The generated JSON matches the downstream Airflow schema and has been validated end to end.

Notes

  • The workflow runs on a scheduled interval and supports manual execution from the Actions UI.
  • No non public APIs are used.

Checklist

  • Uses only public GitHub APIs
  • Snapshot validated with downstream Airflow ingestion
  • Scheduled workflow configured

docs/doxygen_build

# CMake build artifacts
__cmake_systeminformation/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

? Why did we delete this?

.gitignore Outdated
# exclude venv
venv/

.venv/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.venv/
.venv/

I think a new line here is prettier

.github/actions/*/node_modules/
models/experimental/petr/resources/*.pth

.claude
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HUH ? Are we sure we don't want to ignore this?

query {
repository(owner: "tenstorrent", name: "tt-metal") {
mergeQueue {
entries(first: 100) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe leave a cleanup ticket for yourself and let people know that there is a maximum of 100 for now... I don't think we'll see more than 100 at a time, for a while. But something low priority to look at, but be aware of

@arshahTT arshahTT force-pushed the ashah-merge-queue-data branch from e9f6695 to af242d5 Compare February 14, 2026 03:31
Copy link
Collaborator

@tt-rkim tt-rkim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some more general comments:

  • Whenever you make network requests (for example, any gh api calls etc.), you should generally put a timeout for it. You can use timeout-minutes for a step or for the whole job. whole job may be simpler, since we're firing this every 5 min anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants