continuedev / continuedev/continue
Suggestion to make a proper fork
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Issue Category
Documentation organization issue
Affected Documentation Page URL
No response
Issue Description
Since Continue.dev has closed down the discussion section, I can only create this enquiry here.
I absolutely loved Continue.dev and the way to work with ai's and I am sad to see continue.dev go..
Therefore, I suggest we fork it, and I would absolutely love to help maintaining, even though i've never actually contributed properly to open source, so I would love to have somebody else with me in this endeavour to just push me in the right direction.
I thought of a couple of names to help keep the project memorable yet of course distinguishable:
- Continued
- Continuation
- whiletrue
If you know of a better forum or place this content should be placed, please point me in the right direction..
And at last, a big thank you to the continue.dev team which I have nothing but admiration for.
Expected Content
No response
Contributor guide
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 documentation page, file, test, or implementation entry point is identified. Clarify where a fork proposal belongs and define the repository, scope, ownership, and first concrete change before work can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100