docs: link bug reports to central discussion

[Mehdi-Bl]

Adds a README section routing bug reports and issue triage to the shared discussion thread:\n\n- https://github.com/codingworkflow/ai-code-fusion/discussions/151\n\nThis centralizes intake for both claude-code-api and ai-code-fusion.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds documentation to route bug reports and support requests for both claude-code-api and ai-code-fusion to a shared GitHub Discussions thread, centralizing issue intake.

File-Level Changes

Change	Details	Files
Document centralized bug report and support flow via a shared GitHub Discussions thread.	Add a new "Bug Reports & Support" section to the README Instruct users of both claude-code-api and ai-code-fusion to use the shared discussion thread for bug reports and troubleshooting Include a direct link to the GitHub Discussions thread for issues and support	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Add centralized bug report discussion link to README

📝 Documentation

Walkthroughs

Description

• Adds new README section routing bug reports to centralized discussion
• Centralizes issue intake for both claude-code-api and ai-code-fusion projects
• Improves user guidance for reporting bugs and troubleshooting

Diagram

flowchart LR
  README["README.md"]
  README -- "adds Bug Reports & Support section" --> Discussion["Centralized Discussion Thread #151"]

Loading

File Changes

1. README.md 📝 Documentation +6/-0

Add bug reports routing section with discussion link

• Adds new "Bug Reports & Support" section after configuration settings
• Provides centralized discussion thread link for bug reports and troubleshooting
• Applies to both claude-code-api and ai-code-fusion projects
• Positioned before "Developer Docs" section for visibility

README.md

---

[gemini-code-assist]

Summary of Changes

Hello @Mehdi-Bl, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's documentation by introducing a dedicated section in the README.md for bug reports and support. The primary goal is to streamline the process for users seeking assistance or reporting issues by directing them to a single, centralized discussion thread, thereby improving efficiency and consistency in handling community feedback for related projects.

Highlights

• Documentation Update: A new section titled 'Bug Reports & Support' has been added to the README.md file.
• Centralized Support: The new section directs users of claude-code-api and ai-code-fusion to a specific GitHub discussion thread for bug reports and troubleshooting, centralizing support intake.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• README.md
  • Added a new 'Bug Reports & Support' section.
  • Included a link to the central GitHub discussion thread for issue reporting and troubleshooting.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

The pull request successfully adds a 'Bug Reports & Support' section to the README.md file. This change correctly directs users to a centralized GitHub discussion thread for troubleshooting and bug reporting across the related projects, which helps in streamlining issue triage. The markdown formatting is correct and the placement of the new section is logical.

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Misroutes bug reports 🐞 Bug ✓ Correctness

Description

README now directs bug reports to an external ai-code-fusion discussion, conflicting with this
repo’s identity and advertised Issues URL; users/tools will likely file problems in the wrong place.
This fragments triage and breaks expectations from project metadata.

Code

README.md[R96-100]

+## Bug Reports & Support
+
+For `claude-code-api` and `ai-code-fusion`, use this discussion thread for bug reports and troubleshooting:
+
+- https://github.com/codingworkflow/ai-code-fusion/discussions/151

Evidence

The README identifies the project as Claude Code API and instructs cloning from the claude-code-api
repo, but the new bug-report instruction points to an ai-code-fusion discussion. Additionally,
project metadata advertises a different Issues URL than the README guidance, increasing the chance
of misrouted reports.

README.md[12-18]
README.md[96-100]
pyproject.toml[63-68]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The README’s new bug-report instruction points to a different repository than this project’s clone URL and advertised `project.urls.Issues`, likely misdirecting users and fragmenting triage.

### Issue Context
- README is for “Claude Code API Gateway” and clones `codingworkflow/claude-code-api`, but bug reports are routed to `codingworkflow/ai-code-fusion`.
- `pyproject.toml` advertises an Issues URL that doesn’t match the new README guidance.

### Fix Focus Areas
- README.md[96-100]
- pyproject.toml[63-68]
- README.md[12-18] (for consistency check)

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. No security-reporting route 🐞 Bug ⛨ Security

Description

Routing “bug reports and troubleshooting” to a public discussion thread risks accidental public
disclosure of vulnerabilities. Add a short security disclosure note (private channel) alongside the
public support link.

Code

README.md[R96-100]

+## Bug Reports & Support
+
+For `claude-code-api` and `ai-code-fusion`, use this discussion thread for bug reports and troubleshooting:
+
+- https://github.com/codingworkflow/ai-code-fusion/discussions/151

Evidence

The new README section routes all bug reports to a public thread without distinguishing security
vulnerabilities. The codebase includes authentication/API-key handling and explicit security
protections (e.g., path traversal detection), making vulnerability reports plausible and worth
routing via a private channel.

README.md[96-100]
claude_code_api/core/auth.py[66-83]
claude_code_api/core/security.py[50-58]
Best Practice: GitHub security policy / responsible disclosure practice

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
README directs all bug reports to a public discussion thread, but doesn’t provide guidance for reporting security vulnerabilities privately.

### Issue Context
The project includes authentication/API-key handling and other security-sensitive behaviors, so vulnerability reports are plausible; public threads are not ideal for coordinated disclosure.

### Fix Focus Areas
- README.md[96-100]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-free-for-open-source-projects]

1. Misroutes bug reports 🐞 Bug ✓ Correctness

README now directs bug reports to an external ai-code-fusion discussion, conflicting with this
repo’s identity and advertised Issues URL; users/tools will likely file problems in the wrong place.
This fragments triage and breaks expectations from project metadata.

Agent Prompt

### Issue description
The README’s new bug-report instruction points to a different repository than this project’s clone URL and advertised `project.urls.Issues`, likely misdirecting users and fragmenting triage.

### Issue Context
- README is for “Claude Code API Gateway” and clones `codingworkflow/claude-code-api`, but bug reports are routed to `codingworkflow/ai-code-fusion`.
- `pyproject.toml` advertises an Issues URL that doesn’t match the new README guidance.

### Fix Focus Areas
- README.md[96-100]
- pyproject.toml[63-68]
- README.md[12-18] (for consistency check)

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools