vlang / vlang/gitly

[Bug] Wrong issues visible

Open
#248 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
V
Stars
1.5k
Forks
79
PR merge metrics
No merged PRs in 30d

Description

The 'alex/v' repo does not actually have issues, but https://gitly.org/alex/v/issue/1 shows the first ever created issue, which belongs to some other repo.
There is a related problem, that one can see issues of private repositories that way too.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior using the reported gitly.org URL for alex/v/issue/1 and compare it with a repository that actually has issues. Trace how the issue URL resolves its repository and issue, including private repositories. Done means nonexistent repositories do not show another repository's issue and private repository issues are not exposed.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.