Vector35 / Vector35/binaryninja-api
Differentiate remote projects that are on seperate remotes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
I was going through the list of recent projects and opened the "Demo Project" that contained a few demo files, low and behold that project actually was a remote one belonging to a currently inactive remote, It would be nice if in the project browser there was some indication as to which remote "owns" the project, perhaps next to the description.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the project browser and the code that loads remote projects in the Binary Ninja API repository. Trace how project descriptions are presented and how remote ownership is represented, then confirm that projects from separate remotes are visibly distinguishable in the browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, reverse-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100