-
Notifications
You must be signed in to change notification settings - Fork 100
[HUD] Selector for workflow id in commit and PR pages #6919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2bc3a00
to
af070a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit unclear on why workflow_id is being specified here. Based on the PR description, aren't you looking to get the data for a different run attempt on the same job?
You can have multiple workflow runs of a single workflow on the same commit, each of these get a different workflow id, and each of those workflows can have multiple run attempts. This only handles the first one, the second one I put as a TODO in the PR body |
af070a1
to
0dbd4b8
Compare
Gotcha, and the follow up question would be: When is this change useful enough to be worth the extra complextiy? |
It's mostly the TD thing, I want to make it easier to find that info |
When multiple workflows run on the same commit (ex memory leak check + non mem leak check), HUD tries to filter the results so that only the most recent job is shown, but sometimes I want to find older ones.
An unfortunately large change because we usually query jobs for the entire commit instead of workflow by workflow
I reused the commit query because it already queries the necessary fields (name id time duration etc) and didn't want to write another query that we would have to keep in sync
Open to better solutions for how to get this data b/c imo this is kind of ugly
TODO: also handle reruns, better error handling
New


Probably review #6922 first