Skip to content

Conversation

@jordancarlin
Copy link
Collaborator

No description provided.

@github-actions
Copy link

Test Results

2 115 tests  ±0   2 115 ✅ ±0   20m 30s ⏱️ +11s
    1 suites ±0       0 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit c2b7b93. ± Comparison against base commit 7cf10dd.

@Timmmm
Copy link
Collaborator

Timmmm commented Dec 21, 2025

Hmm I'm surprised that's not the default!

@jordancarlin
Copy link
Collaborator Author

Hmm I'm surprised that's not the default!

Agreed, but if you look through the actions log, it clearly isn’t.

@pmundkur pmundkur added the will be merged Scheduled to be merged soon if nobody objects label Dec 22, 2025
@pmundkur pmundkur added this pull request to the merge queue Dec 23, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 23, 2025
@Timmmm
Copy link
Collaborator

Timmmm commented Dec 23, 2025

Hmm seems like it cancelled itself in the merge queue or something?

@jordancarlin
Copy link
Collaborator Author

Hmm. It looks like it ran all of the jobs twice when it was added to the merge queue, and the second instance was cancelled. I’ll look into it. Not sure why the jobs are being run twice, but it looks like that’s actually happening for all PRs when we add them to the merge queue.

@Timmmm Timmmm removed the will be merged Scheduled to be merged soon if nobody objects label Dec 28, 2025
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.

3 participants