Peter Squicciarini

We haven't written the conditionals yet. I think we will need to wrap the current logic of checking out the latest tag.

Sounds good to me @lsmoura

Am not sure which approach to take here: 1. configure .travis.yml in `vscodium-insiders` repo that clones `vscodium` and runs through build process with quality=insider set - setup build to run...

Additionally, it doesn't look like Travis's default deploy tool (which we are currently using) supports uploading releases to a different repo than then the one the build is running on....

Well I've got no idea what was done in https://github.com/microsoft/vscode/pull/107366 :raised_eyebrow: no files were changed. If anyone has any ideas I'm all ears.

I'm wary of investing time into building for Linux 32-bit when MS isn't supporting it, and we haven't even reached feature parity with MS (e.g. they are now building for...

I think this PR takes it a bit too far; the settings/config folders were fresh, so when I downloaded + installed Codium from my branch, it had none of my...

Sorry for the huge delay on this everyone. I don't have much time for VSCodium work these days. This PR can be merged after conflicts are resolved and after I...

@daiyam since this is a big disruptive change, I think it would be better to first introduce a way for non-Github-users to be notified of "big disruptive changes", e.g. #599...

I think wherever something is named "vscode" we can leave ours as "vscodium" (are there any such examples?), and wherever something is named "code" we will have "codium" (e.g. snapcraft,...