Skip to content

chore: sync openapi.json with upstream API #304

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

Merged
sachiniyer merged 1 commit into from
May 27, 2026
Merged

chore: sync openapi.json with upstream API #304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions openapi.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,9 @@
},
"BugReview": {
"properties": {
"asanaStateName": {
"type": "string"
},
"createdAt": {
"type": "integer"
},
Expand Down Expand Up @@ -179,6 +182,7 @@
"review",
"linear",
"jira",
"asana",

@devin-ai-integration devin-ai-integration Bot May 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

📝 Info: BugSource not re-exported — new variant has no downstream impact

The BugSource type is notably absent from the re-export list at src/api/types.rs:7-12. It exists only as a field type within BugReview.source (which is itself optional). No code in the repository pattern-matches on BugSource variants, so adding "asana" is purely additive with zero risk of breaking existing match arms. If a future PR needs to display the source (e.g., in a card view), it would need to handle the new variant at that point.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

"github_issue",
"bug_fix_check"
],
Expand Down
Loading