Where Can I Find the Kaneo Issue Tracker? GitHub Issues Location & API Access

Kaneo uses GitHub Issues as its primary issue tracker, located at https://github.com/usekaneo/kaneo/issues, with structured templates for bug reports, feature requests, and questions.

The Kaneo project — an open-source platform — manages all bug reports, feature requests, and community questions through GitHub's native Issues system. Understanding where to find the issue tracker and how to interact with it programmatically helps contributors and integrators engage effectively with the project.

Kaneo Issue Tracker Location

The official issue tracker for Kaneo is hosted directly on GitHub:

• URL: https://github.com/usekaneo/kaneo/issues

This page displays all open and closed issues, with filtering and search capabilities built into the GitHub interface. The repository maintains the issue tracker within the same codebase as the project source, ensuring seamless integration between code changes and issue resolution.

Issue Templates and Structure

Kaneo provides three structured issue templates to standardize contributor submissions. These templates live in the .github/ISSUE_TEMPLATE/ directory:

Template	File Path	Purpose
Bug report	[.github/ISSUE_TEMPLATE/bug_report.yml](https://github.com/usekaneo/kaneo/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml)	Structured form for reporting defects with environment details and reproduction steps
Feature request	[.github/ISSUE_TEMPLATE/feature_request.yml](https://github.com/usekaneo/kaneo/blob/main/.github/ISSUE_TEMPLATE/feature_request.yml)	Guided template for proposing new functionality
General question	[.github/ISSUE_TEMPLATE/question.md](https://github.com/usekaneo/kaneo/blob/main/.github/ISSUE_TEMPLATE/question.md)	Markdown template for community discussions and clarifications

These files ensure that submitted issues contain consistent, actionable information for maintainers.

Automated Issue Notifications

The project includes a GitHub Actions workflow that triggers when new issues are opened. Located at [.github/workflows/issue-notify.yml](https://github.com/usekaneo/kaneo/blob/main/.github/workflows/issue-notify.yml), this automation alerts the core team immediately upon issue creation, reducing response time for critical bugs.

Accessing Issues Programmatically

For developers building integrations or analyzing project activity, Kaneo's GitHub Issues can be accessed through multiple interfaces.

GitHub CLI

List open issues directly from your terminal:

gh issue list --repo usekaneo/kaneo --state open

Filter by label, assignee, or state using additional flags:

gh issue list --repo usekaneo/kaneo --state all --label bug

GitHub REST API

Fetch open issues programmatically using Node.js:

import fetch from "node-fetch";

const owner = "usekaneo";
const repo = "kaneo";
const url = `https://api.github.com/repos/${owner}/${repo}/issues?state=open`;

const response = await fetch(url, {
  headers: { Accept: "application/vnd.github+json" },
});
const issues = await response.json();

console.log(issues);

This returns issue data including titles, numbers, labels, assignees, and creation timestamps.

Creating Issues via API

Submit new issues programmatically using cURL:

curl -X POST \
  -H "Authorization: token YOUR_GITHUB_TOKEN" \
  -H "Accept: application/vnd.github+json" \
  https://api.github.com/repos/usekaneo/kaneo/issues \
  -d '{"title":"Example bug","body":"Description of the bug"}'

Replace YOUR_GITHUB_TOKEN with a personal access token that has repo scope permissions.

Navigating from the README

The README.md file in the repository root contains a direct link to the Issues page, typically displayed as a GitHub badge near the top of the document. This provides immediate discoverability for new visitors evaluating the project's community health.

Summary

• The Kaneo issue tracker is located at https://github.com/usekaneo/kaneo/issues
• Three issue templates standardize submissions: bug reports, feature requests, and questions
• The notification workflow at .github/workflows/issue-notify.yml alerts maintainers automatically
• The GitHub CLI, REST API, and cURL all support programmatic issue access and creation
• The README.md provides quick navigation to issues via badges and links

Frequently Asked Questions

Does Kaneo use GitHub Issues exclusively for bug tracking?

Yes. According to the usekaneo/kaneo source code, the project relies entirely on GitHub Issues for bug reports, feature requests, and general questions. No external ticketing system is referenced in the repository configuration.

What information do I need to include in a Kaneo bug report?

The bug report template at .github/ISSUE_TEMPLATE/bug_report.yml requires environment details, steps to reproduce, expected behavior, and actual behavior. Following this structure ensures maintainers can triage effectively.

Can I receive notifications for new issues without watching the entire repository?

Yes. Use the GitHub API polling approach shown above, or configure webhook integrations pointing to .github/workflows/issue-notify.yml to build custom notification pipelines without repository-level subscriptions.

How can I search existing issues before creating a duplicate?

Use the GitHub Issues search bar at https://github.com/usekaneo/kaneo/issues with keywords, or run gh issue list --repo usekaneo/kaneo --search "your keyword" to filter programmatically before submission.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}