# How to Report Bugs or Suggest Features for DeepSeek-Reasonix

> Effectively report bugs or suggest features for DeepSeek-Reasonix using structured GitHub Issues and YAML templates. Provide clear details for efficient feedback triage.

- Repository: [YHH/DeepSeek-Reasonix](https://github.com/esengine/DeepSeek-Reasonix)
- Tags: how-to-guide
- Published: 2026-06-26

---

**DeepSeek-Reasonix uses GitHub Issues with structured YAML templates to collect bug reports and feature requests, requiring specific environment details and reproduction steps to ensure maintainers can triage feedback efficiently.**

The DeepSeek-Reasonix repository by esengine provides a standardized workflow for community contributions. When you encounter errors or envision enhancements, you must report bugs or suggest features for DeepSeek-Reasonix through the repository's GitHub issue tracker, which enforces structured templates to ensure clarity and actionability.

## Using the GitHub Issue Templates

The repository provides two dedicated YAML templates located in the `.github/ISSUE_TEMPLATE/` directory. These templates enforce a consistent structure that helps maintainers reproduce bugs and evaluate feature proposals quickly.

### Bug Report Template

The [`.github/ISSUE_TEMPLATE/bug_report.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml) file defines the required fields for submitting defects. This template captures reproducible steps, expected versus actual behavior, environment details, and relevant logs. When you select the **Bug report** template in the GitHub web interface, you must fill in fields describing the problem, steps to reproduce, and your system configuration.

### Feature Request Template

The [`.github/ISSUE_TEMPLATE/feature_request.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/.github/ISSUE_TEMPLATE/feature_request.yml) file governs suggestions for new capabilities. This template requires you to describe the desired improvement, its motivation, and any relevant use-case details. Using this template ensures the maintainers understand the context and potential impact before any code changes are discussed.

## Required Information for Bug Reports

According to the [`CONTRIBUTING.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/CONTRIBUTING.md) file, specifically the "Reporting issues" section at lines 48-55, the maintainers require specific fields to diagnose problems effectively. You must provide:

- **Steps to reproduce** the error in a fresh environment
- **Expected behavior** versus **actual behavior** observed
- **Go version** and **operating system** details
- **Relevant logs** or stack traces from the failure

Providing a well-filled template helps the maintainers triage quickly and ensures the problem is reproducible.

## Methods for Submitting Issues

You can report bugs or suggest features for DeepSeek-Reasonix through three primary interfaces: the GitHub web UI, the GitHub CLI, or the REST API.

### GitHub Web Interface

The recommended method for most users involves the GitHub web interface:

1. Navigate to the **Issues** tab of the repository.
2. Click **New issue**.
3. Select either **Bug report** or **Feature request**.
4. Fill in the structured fields provided by the template.
5. Submit the issue.

When filling out a bug report, follow this format for the description:

```markdown
**Describe the bug**
The `reasonix run` command crashes when the model name contains a dash.

**Steps to reproduce**
1. `reasonix run --model deepseek-pro "test"`
2. Observe the panic stack trace.

**Expected behavior**
The command should execute without crashing.

**Actual behavior**
Panic: interface conversion: interface {} is nil, not string

**Go version and OS**
go version go1.22 linux/amd64

**Relevant logs**

```

### GitHub CLI

If you prefer terminal-based workflows, use the `gh` command-line tool to create templated issues:

```bash

# Install gh if needed

brew install gh   # macOS

sudo apt install gh   # Debian/Ubuntu

# Authenticate (you'll be prompted for a token)

gh auth login

# Open a bug report

gh issue create \
  --title "Crash when model name contains a dash" \
  --body-file ./my-bug-report.md \
  --label bug

```

Ensure your [`my-bug-report.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/my-bug-report.md) file contains the same sections as the web template, including environment details and reproduction steps.

### GitHub REST API

For advanced automation or CI/CD pipelines, use the GitHub REST API with a personal access token (PAT) that has `repo` scope. Never hard-code tokens; retrieve them securely using `gh auth token` or environment variables:

```bash
#!/usr/bin/env bash
TOKEN=$(gh auth token)   # fetches the stored PAT

REPO="esengine/DeepSeek-Reasonix"

curl -X POST \
  -H "Authorization: token $TOKEN" \
  -H "Accept: application/vnd.github+json" \
  https://api.github.com/repos/$REPO/issues \
  -d '{
    "title": "Add support for custom tool registration",
    "body": "## Feature request\n\nI would like to be able to register user-defined tools at runtime ...",

    "labels": ["enhancement"]
  }'

```

## Key Files in the Repository

Understanding the repository structure helps you locate relevant documentation:

- **[`.github/ISSUE_TEMPLATE/bug_report.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml)** – Structured template for submitting bugs
- **[`.github/ISSUE_TEMPLATE/feature_request.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/.github/ISSUE_TEMPLATE/feature_request.yml)** – Structured template for suggesting new features
- **[`CONTRIBUTING.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/CONTRIBUTING.md)** – Full contribution workflow including the "Reporting issues" section
- **[`README.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/README.md)** – General project overview with links to the issue tracker

## Summary

- **DeepSeek-Reasonix** uses GitHub Issues with YAML templates located in `.github/ISSUE_TEMPLATE/` to standardize bug reports and feature requests.
- The **[`CONTRIBUTING.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/CONTRIBUTING.md)** file at lines 48-55 specifies required fields: reproduction steps, expected vs. actual behavior, Go version, OS, and logs.
- Submit via the **GitHub web UI** for guided templates, use **`gh issue create`** for CLI workflows, or leverage the **REST API** for automated submissions.
- Always provide complete environment details and clear reproduction steps to ensure maintainers can triage your feedback efficiently.

## Frequently Asked Questions

### Where are the issue templates stored in the repository?

The templates are stored in the `.github/ISSUE_TEMPLATE/` directory. The [`bug_report.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/bug_report.yml) file handles defect submissions, while [`feature_request.yml`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/feature_request.yml) manages enhancement proposals. Both files enforce structured data collection through GitHub's issue forms feature.

### What information must I include in a bug report?

According to the [`CONTRIBUTING.md`](https://github.com/esengine/DeepSeek-Reasonix/blob/main/CONTRIBUTING.md) file, you must include steps to reproduce, expected versus actual behavior, your Go version, operating system details, and any relevant logs or stack traces. This information appears in the "Reporting issues" section between lines 48-55.

### Can I create issues without using the web browser?

Yes. You can use the **GitHub CLI** (`gh issue create`) with a local markdown file containing the template sections, or submit programmatically via the **GitHub REST API** using a personal access token with `repo` scope. Both methods respect the same data requirements as the web interface.

### How do I suggest a new feature for DeepSeek-Reasonix?

Select the **Feature request** template when creating a new GitHub issue. Describe the desired functionality, explain the motivation behind the request, and provide specific use-case details. This structured approach allows the community to discuss the proposal before implementation begins.