Nayjest/Gito

Possibility to mark issues as irrelevent / hallucinations to avoid further reporting

Open

#203 opened on Jan 12, 2026

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (33 forks)auto 404
aspect: coreaspect: feature-richdiscussionenhancementhelp wantedidea

Repository metrics

Stars
 (381 stars)
PR merge metrics
 (PR metrics pending)

Description

Showld work via github comments. Something like

gito mark issues 1,2,3 as irrelevant

Q: where to store it?

  • orphan repo branch?
  • .gito/config.toml?
  • .gito/irrelevant_issues?

Q: how to match it? Similarity / +structural similarity? Reuse in prompts? Q: auto-generate irrelevance reasons by llm / give possibility to provide additional comment from user? Q: use it somehow in prompts? Match by similarity and ask LLM to approve?

Contributor guide

Research direction
Explore storage options like orphan branch or config file for storing irrelevant issue IDs. Investigate similarity matching (e.g., using embeddings or simple text overlap) to detect duplicates. Consider implementing a comment command to mark issues.
Tech stack
python
Domain
devtools
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40