DeepSeek/awesome-deepseek-integration
1
0
Fork 0
mirror of https://github.com/deepseek-ai/awesome-deepseek-integration synced 2025-01-22 10:35:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update continue.dev README.md

Browse Source
This commit is contained in:
XieJiSS 2024-07-02 14:47:44 +08:00 committed by GitHub
parent 04b68a8704
commit c862a118f6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/continue/README.md
View File

@ -19,7 +19,16 @@ Please use the following config before we release official FIM support:
```json
{
"models": [],
"models": [{
"title": "DeepSeek",
"provider": "openai",
"model": "deepseek-coder",
"apiBase": "https://api.deepseek.com",
"apiType": "openai",
"apikey": REDACTED,
"useLegacyCompletionsEndpoint": false,
"contextLength": 8192
}],
"tabAutocompleteOptions": {
"template": "Please teach me what I should write in the `hole` tag, but without any further explanation and code backticks, i.e., as if you are directly outputting to a code editor. It can be codes or comments or strings. Don't provide existing & repetitive codes. If the provided prefix and suffix contain incomplete code and statement, your response should be able to be directly concatenated to the provided prefix and suffix. Also note that I may tell you what I'd like to write inside comments. \n{{{prefix}}}<hole></hole>{{{suffix}}}\n\nPlease be aware of the environment the hole is placed, e.g., inside strings or comments or code blocks, and please don't wrap your response in ```. You should always provide non-empty output.\n",
"useCache": true,