Open JimXiongGM opened 2 hours ago
👀 @JimXiongGM
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. Please make sure you have given us as much context as possible.\ 非常感谢您提交 issue。我们会尽快调查此事,并尽快回复您。 请确保您已经提供了尽可能多的背景信息。
Hey @JimXiongGM! 👋 I'm here to help you with any bugs, questions, or becoming a contributor. Let's squash those bugs together!
To resolve the issue of Vercel not being able to automatically upgrade after forking a repository, follow these steps:
Delete the Original Repository: If you initially deployed the project without forking, delete that deployment.
Fork the Original Project: Use the Fork button on the original project's GitHub page to create a fork.
Redeploy on Vercel: Deploy the forked repository on Vercel.
Enable GitHub Actions: After forking, manually enable Workflows on the Actions page of your forked project and start the Upstream Sync Action.
Manual Sync if Needed: If you encounter a sync failure, manually click "Update Branch" once.
These steps should help resolve errors like "The provided GitHub repository can't be found" or "The provided GitHub repository does not contain the requested branch or commit reference" by ensuring that Vercel is correctly linked to a forked repository with enabled workflows [1].
To continue talking to Dosu, mention @dosu.
📝 Reference
https://github.com/lobehub/lobe-chat/tree/main/docs/self-hosting/advanced/upstream-sync.zh-CN.mdx
🐛 Feedback
Unable to automatically upgrade on Vercel.
After deleting repo, fork repo, and clicking
Redeploy
to reconnect the repository to the fork, it showsThe provided GitHub repository can't be found.
orThe provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.