OpenCloning / OpenCloning/OpenCloning_backend
Store overhang info in gb file
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 11
- Avg merge
- 14m
- Merged PRs (30d)
- 5
Description
Not use the json fields, instead put it somewhere in the gb info
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
No files, tests, or entry points are named. Start by locating the code that writes the JSON fields and GB output, then determine where GB metadata is represented; done means overhang information is stored in the GB info instead of those JSON fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100