Skip to content

fix(): Add cost-confidence to status parsing. #607

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 26, 2025
Merged

fix(): Add cost-confidence to status parsing. #607

merged 1 commit into from
Jun 26, 2025

Conversation

aidanCQ
Copy link
Contributor

@aidanCQ aidanCQ commented Jun 26, 2025 •
edited
Loading

Job Status API should be able to return “cost-confidence” value when it is present - this will be set on Syntax Check jobs and informs the customer if their job is dynamic or not. It will be an integer value between 0 and 100, inclusive.

@aidanCQ aidanCQ requested a review from yao-cqc as a code owner June 26, 2025 09:22
@aidanCQ aidanCQ merged commit 5d2c142 into main Jun 26, 2025
8 of 9 checks passed
@aidanCQ aidanCQ deleted the feat/add-more-status-fields-to-parsing-fn-2 branch June 26, 2025 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yao-cqc yao-cqc yao-cqc approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@aidanCQ @yao-cqc