feat: view Support tickets and tighten submissions - #11
Merged
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthroughAdds a read-only ChangesSupport ticket viewing
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant supportViewCommand
participant SupportSession
participant SupportPortal
participant parseSupportTicketDetails
User->>supportViewCommand: request ticket
supportViewCommand->>SupportSession: authenticate and viewTicket
SupportSession->>SupportPortal: fetch ticket page
SupportPortal-->>SupportSession: ticket HTML
SupportSession->>parseSupportTicketDetails: parse ticket HTML
parseSupportTicketDetails-->>SupportSession: ticket details
SupportSession-->>supportViewCommand: normalized ticket
supportViewCommand-->>User: table or JSON output
Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:L
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
Comment on lines
+13
to
+19
| function ticketOutput(ticket: SupportTicketDetails, account: string | undefined) { | ||
| return { | ||
| ticket: ticket.ticketId, | ||
| subject: ticket.subject, | ||
| status: ticket.status, | ||
| account: account ?? ticket.author, | ||
| scope: ticket.scope, |
There was a problem hiding this comment.
Suggestion: The JSON and table account field is populated from the authenticated GitHub login, which is not necessarily the Support account represented by the ticket. Organization tickets will consequently report the viewer's login instead of the ticket account; derive this value from the parsed scope or expose the authenticated identity under a separate field. [api mismatch]
Severity Level: Major ⚠️
- ⚠️ Organization ticket metadata reports the viewer account.
- ⚠️ JSON consumers receive an incorrect account field.
- ⚠️ Table output can confuse authors with Support accounts.
(Use Cmd/Ctrl + Click for best experience)
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** src/commands/support/view.ts
**Line:** 13:19
**Comment:**
*Api Mismatch: The JSON and table `account` field is populated from the authenticated GitHub login, which is not necessarily the Support account represented by the ticket. Organization tickets will consequently report the viewer's login instead of the ticket account; derive this value from the parsed scope or expose the authenticated identity under a separate field.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
Changes
gh2 support viewcommand with table and JSON output--yessubmissionsmainhistoryTesting
bun run typecheckbun test(124 tests)bun run buildnpm pack --dry-runNotes
CodeAnt-AI Description
Add read-only Support ticket viewing and submission guidance
What Changed
gh2 support viewto display a ticket’s metadata, original body, and replies in chronological order--yesImpact
✅ Faster access to complete Support ticket history✅ Safer Support submissions✅ Consistent ticket data for scripts💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit
New Features
gh support viewfor viewing GitHub Support ticket details and comments.Documentation