## Background This is a follow-up epic that captures the 3rd phase of the project that improves the process of updating the GitLab VSCode Fork. You can find more information about the motivation, goals, business value, and technical strategy for this project in the phase 1 epic: https://gitlab.com/groups/gitlab-org/-/epics/12951 ## Description Identifying new VSCode releases and scheduling fork upgrades is not a predictable and standardized process. VSCode upgrades are only scheduled where the IDE group is interested in a feature included in a new release. Since there isn't an upgrade issue created in advanced, upgrading the VSCode fork is not taken into consideration during the high-level planning phase. There isn’t an issue template that describes the acceptance criteria to approve an upgrade or lists the steps to run the process. #### Proposal * Implement a scheduled CI job that identifies new VSCode releases and creates an upgrade issue. * Create an issue template that describes instructions to run the entire VSCode upgrade process. #### Benefits * Create a predictable VSCode fork upgrade cadence and allow stakeholders to consider this task in the high-level planning meetings. * Standardize the acceptance criteria and the instructions to run a VSCode fork upgrade. * Flattens the learning curve to run the upgrade process. ### Publish VSCode releases from a CI job Currently, [creating a VSCode fork release](https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/blob/main/GL_FORK_PROCESS.md?ref_type=heads#creating-release) entails running a script in your local environment and pushing a tag to the remote repository. The entire process is automated which would save us considerable time during the upgrade process. #### Proposal * Create a CI job that create a new `tag` for the latest VSCode release. * Create a CI job that pushes artifacts to the package registry for the most recent tag and also publish a new release page. #### Benefits * Flattens the learning curve to run the upgrade process. * Reduces human error by automating the steps that don’t require human intervention. ## Deliverables * [ ]   https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/issues/41+ * [ ] [Create an "Upgrade VSCode Fork" issue and merge request templates](https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/issues/40 "Create issue and merge request templates for uprading VSCode Fork") * [ ] [Schedule a CI job that detects new VSCode releases and create an upgrade issue and an upgrade MR](https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/issues/29 "Schedule a CI job that detects new VSCode releases and create an upgrade issue and an upgrade MR")