CI: different pipelines for this repo and generated templates

[uint]

• It doesn't seem to make much sense to deploy the template to gitpod.
  * It would make sense to set up some automatic testing of the template (generate a template -> run a bunch of commands like cargo test, cargo schema, etc).

At a glance, it looks like this might be possible with pre-hooks:

https://cargo-generate.github.io/cargo-generate/templates/scripting.html

[webmaster128]

2. is done using Appveyor. See the meta folder and Fix Appveyor CI config #132

[uint]

Ah, I see

[webmaster128]

There might be better options, but using Appveyor worked for years for this use case.

I don't know about gitpod. Orkun created it. Would be good to understand how this is used.

[uint]

There might be better options

Nah, I just assumed we had nothing for testing the template because nothing seemed to run on PRs. If we have something, I'm happy.

[uint]

@orkunkl What's the gitpod for? It looks pretty unused. It's only triggered for the master branch (which doesn't exist) and tags (last one was a while ago).

Is it meant to only be built for the cw-template repo and not generated projects?

[orkunkl]

Gitpod is an vscode coding environment on the browser. The idea back then putting in gitpod to generated repos to enable devs to be able to open up an environment. Then Oraichain team built an IDE that works with vscode and gitpod enabling cw development on browser(like remix ide). @ducphamle2 is running the cw ide project. He can give ideas if the .gitpod is necessary here.

[ducphamle2]

@orkunkl Thank you for referencing the IDE. Basically with Gitpod, you can put .gitpod.yml file in the root of the workspace and choose the git repo URL through the IDE (works with any branch, not just master), then it will create the dev environment with the repo you want. I don't know if that's what you guys currently need or not