mdahwireng / mdahwireng/GitHub_Analyzer_API
Create endpoints for code analysis for given repos other than all repos in a users repository.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Filtering out all files which are not in the target group (files of languages to carry analysis on) takes a long time. Therefore, creating endpoints for analysis for a given repo will result in an efficient use of time.
This may bring about 2 extra endpoints, one for python codes analysis and the other for JS codes analysis
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 existing repository-wide analysis endpoints and the Python and JavaScript analysis entry points. Define how a repository-specific request identifies its target repo and confirm that analysis skips unrelated repositories and files. Done means the Python and JavaScript endpoints analyze only the requested repository and return the expected results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100