mrva/vscode-codeql
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
89b6b5a9457e23f300a7d3d4904f4648ed291a05
vscode-codeql/.github/ISSUE_TEMPLATE/new-extension-release.md
Jason Reed 963ff9f458 Change references to master branch to main branch 
I have already pushed `main` upstream pointing at the same commit as
master, so this PR should be safe to merge. To the best of my
knowledge all that's necessary after that is to change the
default branch
in https://github.com/github/vscode-codeql/settings/branches.
2020-06-16 14:00:02 -04:00

1019 B
Raw Blame History

name, about, title, labels, assignees
name about title labels assignees
New extension release Create an issue with a checklist for the release steps (write access required for the steps) Release Checklist for version xx.xx.xx
  • Update this issue title to refer to the version of the release
  • Trigger a release build on Actions by adding a new tag on branch main of the format vxx.xx.xx
  • Monitor the status of the release build in the Release workflow in the Actions tab.
  • Download the VSIX from the draft GitHub release that is created when the release build finishes.
  • Log into the Visual Studio Marketplace.
  • Click the ... menu in the CodeQL row and click Update.
  • Drag the .vsix file you downloaded from the GitHub release into the Marketplace and click Upload.
  • Publish the draft GitHub release and confirm the new release is marked as the latest release at https://github.com/github/vscode-codeql/releases.