📚 DOCS: Update publishing steps

Author: chrisjsewell

.github/workflows/ci.yml

@@ -4,6 +4,8 @@ name: CI
 on:
   push:
     branches: [master, ci-*]
+    tags:
+    - "v[0-9]+.[0-9]+.[0-9]+*"
   pull_request:
     branches: [master]
 
@@ -65,9 +67,9 @@ jobs:
 
   publish:
     # only if all tests complete and the commit is tagged as a release
-    name: Publish to Marketplace
+    name: Publish to VS Code Marketplace
     needs: [lint, tests]
-    if: github.event_name == 'push' && startsWith(github.event.ref, 'refs/tags') && contains(github.ref, 'release')
+    if: github.event_name == 'push' && startsWith(github.event.ref, 'refs/tags') && contains(github.ref, 'v')
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v2

README.md

@@ -171,14 +171,13 @@ $ npm run lint:fix
 
 ### Publishing to VS Marketplace
 
-The publishing of the package should be done *via* the Github Actions CI.
-To trigger a release:
+The publishing of the package should be done *via* the Github Actions CI:
 
 1. Bump the version with npm, e.g. `npm version patch -m "🚀 RELEASE: v%s"` (major/minor/patch based on [semantic versioning](https://semver.org/))
 2. Push the commit and tag generated by npm (`git push --follow-tags`)
-3. Create a new release tag on Github starting with `release`, e.g. `release-0.9.4`.
+3. This should trigger the CI action and the `publish` step, check it runs correctly.
 
-See also: <https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions>
+See also: <https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions>, and the [ExecutableBookProject publisher organization](https://dev.azure.com/ExecutableBookProject).
 
 ## Acknowledgements