Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Join a new service provider gitee #860

Closed
wants to merge 2 commits into from
Closed

Join a new service provider gitee #860

wants to merge 2 commits into from

Conversation

mapleafgo
Copy link

@mapleafgo mapleafgo commented Apr 24, 2019

Short description of what this resolves:

Github access is slow in China, preferring to choose gitee.

How Has This Been Tested?

"gitServer": "gitee"

Checklist:

  • I have read the contribution guidelines.
  • My change requires a change to the documentation and GitHub Wiki.
  • I have updated the documentation and Wiki accordingly.

@shanalikhan
Copy link
Owner

I dont want to use new service.
There is already #413 opened that allows repo sync which you can use for gitee in future.

@mapleafgo
Copy link
Author

mapleafgo commented Apr 25, 2019

@shanalikhan Thank you for your reply. I want to release the version of gitee to the vscode extension synchronously. Is that okay?

@shanalikhan
Copy link
Owner

What we can do is:
You can decouple the existing githubservice as generic generic service for upload / download.
Once it is done, you need to write githubservice that will be used for github by using the existing github code.

After that you can create new folder for custom services where you can write your own service for gitee gists.
gitee users needs to run some command to build it using the giteeservice file, or we can provide custom builds for gitee that can be downloaded separately by providing the link from the readme.

@mapleafgo
Copy link
Author

Thank you very much for your advice. I currently add the gitServer parameter to the configuration file to switch services. If you don't use configuration parameters, it's also nice to use a separate build!

Can I merge these operations? Or just build it on my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants