Add a button to improve vecel deploy workflow

[shiyuhang0]

Is your feature request related to a problem? Please describe.

Now, the vercel deploy workflow is unfriendly. Add a button to provide a better user experience

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[hooopo]

I believe that Vercel's template method is not a fork but a copy. In this way, after the users copy the repository, they can no longer synchronize with the upstream repository. Furthermore, they cannot reflect and track the forked repositories on ossinsight-lite.

Please correct me if I've misunderstood.

[zhangyangyu]

I believe that Vercel's template method is not a fork but a copy.

Yes. It's not a fork.

In this way, after the users copy the repository, they can no longer synchronize with the upstream repository. Furthermore, they cannot reflect and track the forked repositories on ossinsight-lite.

IMHO currently the most important thing is to let potential users to have a good installation experience. How many users will keep updating commits from upstream? And if they do want, they could manually add upstream as a git remote to their repo copy and sync between them.

And we could provide both? The button acts as a quick installation way to let users have an experience fast. The fork way works for users that may be interested in continuous developement from upstream.

[hooopo]

@zhangyangyu @shiyuhang0

I just found a Github Action that can synchronize any repository (it doesn't require the target repository to be the parent of the synchronized repository). If this is successful, the deployment button would be a better option.

https://github.com/repo-sync/github-sync