You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -86,13 +88,18 @@ If you have deployed your own project with just one click following the steps ab
86
88
87
89
We recommend that you follow the steps below to re-deploy:
88
90
89
-
- Delete the original repo;
90
-
- Fork this project;
91
-
- Go to the Vercel dashboard, delete the original project, then create a new project and select the project you just forked to redeploy;
92
-
- Please manually add an environment variable named `OPENAI_API_KEY` and enter your API key as the value during the redeploy process.
91
+
- Delete the original repository;
92
+
- Use the fork button in the upper right corner of the page to fork this project;
93
+
- Choose and deploy in Vercel again, [please see the detailed tutorial](./docs/vercel-en.md#how-to-create-a-new-project).
94
+
95
+
## Enable Automatic Updates
96
+
After forking the project, due to the limitations imposed by Github, you need to manually enable Workflows and Upstream Sync Action on the Actions page of the forked project. Once enabled, automatic updates will be scheduled every hour:
This project will be continuously updated, and after forking the project, the upstream code will be automatically synchronized every day without additional operations.
If you want to update instantly, you can check out the [Github documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) to learn how to synchronize a forked project with upstream code.
97
104
98
105
You can star or watch this project or follow author to get release notifictions in time.
0 commit comments