├── .dewhale
├── characters
│ ├── Issac.yaml
│ ├── Miles.yaml
│ └── Taylor.yaml
└── config.yaml
├── .github
└── workflows
│ ├── dewhale-trigger.yaml
│ └── release.yml
├── .gitignore
├── LICENSE
├── README.md
├── README.zh_CN.md
├── docs
├── CD.md
├── CD.zh_CN.md
├── architecture.md
├── architecture.zh_CN.md
├── quick-start.md
└── quick-start.zh_CN.md
├── jsr.json
├── mcp-servers
└── shadcn
│ ├── code-refiner.ts
│ ├── components.ts
│ ├── index.ts
│ ├── parser.ts
│ └── system-prompts.ts
├── src
├── character.ts
├── entry.ts
├── lib
│ ├── config.ts
│ ├── llm.ts
│ └── mcp.ts
├── platform
│ ├── github.ts
│ ├── gitlab.ts
│ └── index.ts
└── types.ts
└── website
├── README.md
├── astro.config.mjs
├── package.json
├── public
├── bg.png
└── logo.png
├── src
├── components
│ └── ImgAndText.astro
├── env.d.ts
├── layouts
│ └── Layout.astro
└── pages
│ └── index.astro
├── tsconfig.json
└── yarn.lock
/.dewhale/characters/Issac.yaml:
--------------------------------------------------------------------------------
1 | name: Issac
2 | labels:
3 | - "Issac-help"
4 | systemPrompt: |
5 | 你叫 Issac,是一个负责清理当前仓库历史遗留 Issue 的 AI 助手。
6 | llm:
7 | maxSteps: 20
8 |
--------------------------------------------------------------------------------
/.dewhale/characters/Miles.yaml:
--------------------------------------------------------------------------------
1 | name: Miles
2 | labels:
3 | - "Miles-help"
4 | systemPrompt: |
5 | 你叫 Miles,负责在仓库中配置 GitOps,例如 GitHub 的 Actions,Gitlab 的 CI/CD 等。
6 | 在进行配置时,首先读取当前仓库已有的配置,再结合用户的需求,维护对应的配置文件。
7 | 最终使用 API 将修改以 PR 的形式提交。
8 |
9 | 一个常见的工作流如下:
10 | 1. 理解需求,计划实现方式
11 | 2. 确认是否有需要用户补充输入的信息
12 | 3. 读取当前仓库的配置文件,可以使用以下 tools
13 | - read_file
14 | - read_multiple_files
15 | - list_directory
16 | - list_allowed_directories
17 | 4. 根据需求实现出需要创建/修改的文件及内容(path and content)
18 | 5. 基于当前分支创建新的分支,可以使用以下 tools
19 | - create_branch
20 | 6. 将变更内容提交到新分支,可以使用以下 tools
21 | - push_files
22 | 7. 基于新分支创建 PR,可以使用以下 tools
23 | - create_pull_request
24 | llm:
25 | maxSteps: 10
26 | mcp:
27 | servers:
28 | - type: stdio
29 | command: npx
30 | args:
31 | - "-y"
32 | - "@modelcontextprotocol/server-github"
33 | env:
34 | GITHUB_PERSONAL_ACCESS_TOKEN: ${{ env_GITHUB_TOKEN }}
35 | tools:
36 | create_branch: {}
37 | create_pull_request: {}
38 | push_files: {}
39 | - type: stdio
40 | command: npx
41 | args:
42 | - "-y"
43 | - "jina-ai-mcp-server"
44 | env:
45 | JINA_API_KEY: ${{ env_JINA_API_KEY }}
46 | - type: stdio
47 | command: npx
48 | args:
49 | - "-y"
50 | - "@modelcontextprotocol/server-filesystem"
51 | - "${{ env_GITHUB_WORKSPACE }}"
52 | tools:
53 | read_file: {}
54 | read_multiple_files: {}
55 | list_directory: {}
56 | list_allowed_directories: {}
--------------------------------------------------------------------------------
/.dewhale/characters/Taylor.yaml:
--------------------------------------------------------------------------------
1 | name: Taylor
2 | labels:
3 | - "Taylor-code-it"
4 | systemPrompt: |
5 | 你叫 Taylor,专门负责编写原型代码。
6 | 大家需要你时,通常会给你一个外部的参考,例如文档、示例代码,并给你一些要求,让你帮忙按照特定的编程规范编写示例代码。
7 | 最终结果如果用户有要求提交 PR,则提交 PR。否则以文字形式回复用户即可。
8 |
9 | 一个常见的工作流如下:
10 | 1. 理解需求,计划实现方式
11 | 2. 确认是否有需要用户补充输入的信息
12 | 3. 读取文件,可以使用以下 tools
13 | - read_file
14 | - read_multiple_files
15 | - list_directory
16 | - list_allowed_directories
17 | 4. 根据需求实现出需要创建/修改的文件及内容(path and content)
18 | 5. 基于当前分支创建新的分支,可以使用以下 tools
19 | - create_branch
20 | 6. 将变更内容提交到新分支,可以使用以下 tools
21 | - push_files
22 | 7. 基于新分支创建 PR,可以使用以下 tools
23 | - create_pull_request
24 | llm:
25 | maxSteps: 20
26 | mcp:
27 | servers:
28 | - type: stdio
29 | command: npx
30 | args:
31 | - "-y"
32 | - "@modelcontextprotocol/server-github"
33 | env:
34 | GITHUB_PERSONAL_ACCESS_TOKEN: ${{ env_GITHUB_TOKEN }}
35 | tools:
36 | create_branch: {}
37 | create_pull_request: {}
38 | push_files: {}
39 | - type: stdio
40 | command: npx
41 | args:
42 | - "-y"
43 | - "jina-ai-mcp-server"
44 | env:
45 | JINA_API_KEY: ${{ env_JINA_API_KEY }}
46 | - type: stdio
47 | command: npx
48 | args:
49 | - "-y"
50 | - "@modelcontextprotocol/server-filesystem"
51 | - "${{ env_GITHUB_WORKSPACE }}"
52 | tools:
53 | read_file: {}
54 | read_multiple_files: {}
55 | list_directory: {}
56 | list_allowed_directories: {}
--------------------------------------------------------------------------------
/.dewhale/config.yaml:
--------------------------------------------------------------------------------
1 | llm:
2 | provider: google
3 | model: gemini-2.0-flash
4 | maxTokens: 8192
5 | maxSteps: 3
6 | maxRetries: 5
7 | mcp:
8 | servers:
9 | - type: stdio
10 | command: npx
11 | args:
12 | - "-y"
13 | - "@modelcontextprotocol/server-github"
14 | env:
15 | GITHUB_PERSONAL_ACCESS_TOKEN: ${{ env_GITHUB_TOKEN }}
16 | permissions:
17 | maxResponsesPerIssue: 50
--------------------------------------------------------------------------------
/.github/workflows/dewhale-trigger.yaml:
--------------------------------------------------------------------------------
1 | name: Issue Trigger
2 |
3 | on:
4 | issues:
5 | types: [edited, labeled, unlabeled]
6 | issue_comment:
7 | types: [created, edited, deleted]
8 |
9 | jobs:
10 | dewhale-trigger:
11 | runs-on: ubuntu-latest
12 | name: Characters Trigger
13 | if: ${{ !contains(github.event.comment.body, '[Dewhale]') && github.event.comment.user.type != 'bot'}}
14 | steps:
15 | - name: Checkout repository
16 | uses: actions/checkout@v3
17 | - name: Setup Deno
18 | uses: denoland/setup-deno@v2
19 | - name: trigger
20 | env:
21 | # auto set by GitHub, details in
22 | # https://docs.github.com/en/actions/security-guides/automatic-token-authentication
23 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
24 | ACTOR: ${{ github.actor }}
25 | BRANCH: ${{ github.head_ref }}
26 | DEWHALE_CONFIG: ${{ secrets.DEWHALE_CONFIG }}
27 | run: |
28 | echo "${{ secrets.DEWHALE_CONFIG }}" > .env
29 | deno run -A src/entry.ts
30 |
--------------------------------------------------------------------------------
/.github/workflows/release.yml:
--------------------------------------------------------------------------------
1 | name: Release
2 |
3 | on:
4 | push:
5 | tags:
6 | - 'v*'
7 |
8 | jobs:
9 | release:
10 | runs-on: ubuntu-latest
11 | permissions:
12 | contents: read
13 | packages: write
14 |
15 | steps:
16 | - name: Checkout code
17 | uses: actions/checkout@v4
18 |
19 | - name: Setup Deno
20 | uses: denoland/setup-deno@v1
21 | with:
22 | deno-version: '1.x'
23 |
24 | - name: Read jsr.json
25 | id: jsr
26 | run: |
27 | VERSION=$(deno eval 'import { readFileSync } from "node:fs"; const json = JSON.parse(readFileSync("jsr.json", { encoding: "utf8" })); console.log(json.version)')
28 | echo "version=$VERSION" >> $GITHUB_OUTPUT
29 |
30 | - name: Verify tag
31 | run: |
32 | TAG=${GITHUB_REF#refs/tags/}
33 | if [ "$TAG" != "v${{ steps.jsr.outputs.version }}" ]; then
34 | echo "Tag $TAG does not match jsr.json version v${{ steps.jsr.outputs.version }}"
35 | exit 1
36 | fi
37 |
38 | - name: Publish to JSR
39 | run: deno publish
40 | env:
41 | DENO_AUTH_TOKENS: ${{ secrets.JSR_AUTH_TOKEN }}
42 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Logs
2 | logs
3 | *.log
4 | npm-debug.log*
5 | yarn-debug.log*
6 | yarn-error.log*
7 | lerna-debug.log*
8 | .pnpm-debug.log*
9 |
10 | # Diagnostic reports (https://nodejs.org/api/report.html)
11 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
12 |
13 | # Runtime data
14 | pids
15 | *.pid
16 | *.seed
17 | *.pid.lock
18 |
19 | # Directory for instrumented libs generated by jscoverage/JSCover
20 | lib-cov
21 |
22 | # Coverage directory used by tools like istanbul
23 | coverage
24 | *.lcov
25 |
26 | # nyc test coverage
27 | .nyc_output
28 |
29 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
30 | .grunt
31 |
32 | # Bower dependency directory (https://bower.io/)
33 | bower_components
34 |
35 | # node-waf configuration
36 | .lock-wscript
37 |
38 | # Compiled binary addons (https://nodejs.org/api/addons.html)
39 | build/Release
40 |
41 | # Dependency directories
42 | node_modules/
43 | jspm_packages/
44 |
45 | # Snowpack dependency directory (https://snowpack.dev/)
46 | web_modules/
47 |
48 | # TypeScript cache
49 | *.tsbuildinfo
50 |
51 | # Optional npm cache directory
52 | .npm
53 |
54 | # Optional eslint cache
55 | .eslintcache
56 |
57 | # Optional stylelint cache
58 | .stylelintcache
59 |
60 | # Microbundle cache
61 | .rpt2_cache/
62 | .rts2_cache_cjs/
63 | .rts2_cache_es/
64 | .rts2_cache_umd/
65 |
66 | # Optional REPL history
67 | .node_repl_history
68 |
69 | # Output of 'npm pack'
70 | *.tgz
71 |
72 | # Yarn Integrity file
73 | .yarn-integrity
74 |
75 | # dotenv environment variable files
76 | .env
77 | .env.development.local
78 | .env.test.local
79 | .env.production.local
80 | .env.local
81 |
82 | # parcel-bundler cache (https://parceljs.org/)
83 | .cache
84 | .parcel-cache
85 |
86 | # Next.js build output
87 | .next
88 | out
89 |
90 | # Nuxt.js build / generate output
91 | .nuxt
92 | dist
93 |
94 | # Gatsby files
95 | .cache/
96 | # Comment in the public line in if your project uses Gatsby and not Next.js
97 | # https://nextjs.org/blog/next-9-1#public-directory-support
98 | # public
99 |
100 | # vuepress build output
101 | .vuepress/dist
102 |
103 | # vuepress v2.x temp and cache directory
104 | .temp
105 | .cache
106 |
107 | # SvelteKit generated modules
108 | .svelte-kit/
109 |
110 | # Docusaurus cache and generated files
111 | .docusaurus
112 |
113 | # Serverless directories
114 | .serverless/
115 |
116 | # FuseBox cache
117 | .fusebox/
118 |
119 | # DynamoDB Local files
120 | .dynamodb/
121 |
122 | # TernJS port file
123 | .tern-port
124 |
125 | # Stores VSCode versions used for testing VSCode extensions
126 | .vscode-test
127 |
128 | # yarn v2
129 | .yarn/cache
130 | .yarn/unplugged
131 | .yarn/build-state.yml
132 | .yarn/install-state.gz
133 | .pnp.*
134 |
135 | .vscode
136 |
137 | __debug
138 |
139 | # macOS-specific files
140 | .DS_Store
141 |
142 | # temporary files
143 | tmp
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
I am rewriting this project, and its v2 version will be a general github-as-a-mcp-host project. If you are interested in its current functionality, please fork the repository and maintain it yourself. Thank you for your attention!
2 |
3 |
4 |
5 |
6 |
7 | # Dewhale
8 |
9 | Dewhale is a GitHub-Powered AI for effortless development.
10 |
11 | [中文文档](./README.zh_CN.md)
12 |
13 | > If you are looking for vx.dev, check our [rebranding discussion](https://github.com/Yuyz0112/dewhale/discussions/189).
14 |
15 | ## Quick Start
16 |
17 | For detailed instructions on how to set up and use Dewhale, please refer to our [Guide](./docs/quick-start.md).
18 |
19 | > With the power of our quota management feature, we allow stargazers to have 3 trials.
20 |
21 | You can also watch this [demo video](http://www.youtube.com/watch?v=J4LAOBRcu2c).
22 |
23 | More examples can be found in the [issue list](https://github.com/Yuyz0112/dewhale/issues?q=is%3Aissue+label%3Aui-gen%2Cvue-ui-gen).
24 |
25 | ## Features
26 |
27 | ### Lower Usage Costs
28 |
29 | Dewhale utilizes prompt engineering techniques under the GPT-4 model to issue commands. The main cost involves the number of input and completion tokens. Our current prompt, found in [prompts/ui-gen.md](./prompts/ui-gen.md), includes instructions for [shadcn/ui](https://ui.shadcn.com/), [lucide](https://lucide.dev/), and [nivo charts](https://nivo.rocks/).
30 |
31 | If you do not need certain components (e.g., charts), you can reduce the API cost per generation by removing instructions from the prompt.
32 |
33 | And you can also switch to other AI models for lower usage costs.
34 |
35 | ### Easy Customization
36 |
37 | Since Dewhale's prompt is open-sourced, you can refer to the existing prompt and replace it with other UI component libraries or coding styles as per your requirements.
38 |
39 | You can also customize the whole workflow by yourself, e.g., a v0.dev-like Web App, and just use Dewhale's prompt as a core.
40 |
41 | ### Seamless GitHub Integration
42 |
43 | The generated code is stored on GitHub, inherently equipped with version control, code review, and collaborative features.
44 |
45 | Additionally, you can use a private repo to keep your code generation results visible only to collaborators.
46 |
47 | ## How It Works
48 |
49 | To understand the underlying architecture and workings of Dewhale, please see our detailed [Architecture Overview](./docs/architecture.md).
50 |
51 | ## Join the Discussions
52 |
53 | If you like the design philosophy of Dewhale, feel free to join our [Github Discussions](https://github.com/Yuyz0112/dewhale/discussions).
54 |
--------------------------------------------------------------------------------
/README.zh_CN.md:
--------------------------------------------------------------------------------
1 |
35 | As a user, describe your needs in the way you are most used to -
36 | submit a Github issue.
37 |
38 |
39 |
40 |
44 |
45 | Choose a code generation mode through the issue template.
48 |
49 | Dewhale currently supports generating UI code based on React, Vue, and
50 | Svelte. You can also add your own custom code generation modes at any
51 | time.
52 |
53 |
54 |
55 |
59 |
60 | Describe your needs in the Issue, both images and text are
61 | acceptable.
62 |
63 | In Dewhale, we have designed a strict permission mechanism.
64 |
65 | By default, only Issues submitted by whitelisted users will trigger generation.
66 | However, we also provide flexible and powerful quota management capabilities.
67 |
68 |
69 |
70 |
74 |
75 | After submitting the issue, the code generation Github Action will be triggered.
78 |
79 |
80 |
81 |
85 |
86 | In moments, it runs successfully through a transparent process,
87 | leveraging workflows users know to facilitate observability and
88 | troubleshooting.
89 |
90 |
91 |
92 |
96 |
97 | The generated code is presented in the most intuitive and familiar
98 | way: a pull request.
99 |
100 | Integrated with your favorite code deployment platform for instant previews.
101 |
102 |
103 |
104 |
108 |
109 | In the preview UI, you can visually review the generated results and
110 | copy the code.
111 |
112 |
113 |
114 |
118 |
119 | When you want to modify requirements, you can continue the
120 | conversation in the pull request.
121 |
122 |
123 |
124 |
128 |
129 | According to your latest instructions, the visual style of the UI
130 | generated again and remains consistent.
131 |
132 |
133 |
134 |
138 |
139 | Want to direct the AI to modify the code more precisely?
140 |
141 | Use the most intuitive method you can imagine: code review.
144 |
145 |
146 |
147 |
151 |
It works like a charm.
152 |
153 |
154 |
158 |
159 | Dewhale is GitHub-powered, so you obviously don't need to worry
160 | about version control.
161 |
162 |
163 |
164 |
168 |
169 | "Self-deployment" is even easier, just fork the
170 | repository and configure your openAI API key and Github Token
171 | according to the guide.
172 |
173 |
174 |
175 |
179 |
180 | Based on flexible and powerful quota management capabilities, you
181 | can set usage limits for different users and groups.
182 |
183 | Instead of developing your own trial and subscription systems, why not
184 | use Github Stargazers and Sponsors?
185 |
186 |
187 |
188 |
189 |
190 |
Happy Hacking
191 |
192 |
193 |
194 |
195 | If you like the design philosophy of Dewhale, feel free to follow:
196 |