Merge pull request #80 from forcedotcom/release-0.6.0

RELEASE @W-15819273@ Releasing v0.6.0

.github/ISSUE_TEMPLATE/0-bug-report.yml

@@ -0,0 +1,107 @@
+name: Report a Bug
+description: Report an issue with the Salesforce Code Analyzer Extension
+title: "[BUG] <YOUR_TITLE_HERE>"
+labels: []
+body:
+- type: dropdown
+  attributes:
+    label: Have you verified this is Salesforce Code Analyzer Extension specific?
+    description: |
+      Oftentimes, issues are not specific to this extension, and can be reproduced with the Salesforce CLI directly. Before creating this issue, please check to see if the same issue occurs when running the [Salesforce Code Analyzer CLI](https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/code-analyzer-command-reference.md) directly. If so, then please report the issue in the [sfdx-scanner repo](https://github.com/forcedotcom/sfdx-scanner/issues) instead. Otherwise, you may create your issue here.
+
+      **I have verified that the issue is only reproducible when running the Salesforce Code Analyzer Extension.**
+      <sup>(You must select "Yes" to create an issue.)</sup>
+    options:
+    - ''
+    - "Yes"
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Bug Description
+    description: Provide a clear and concise description of what the bug is.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: List out the steps that you used to reproduce the bug behavior. Be as specific and clear as possible.
+    placeholder: |
+      1. I first do ...
+      2. Then I do ...
+      3. Lastly, I do ...
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: Provide a clear and concise description of what you expected to happen.
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Operating System
+    description: |
+      What is your machine's operating system?
+    placeholder: |
+      Example: MacOS Sonoma 14.4.1
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Visual Studio Code Version
+    description: |
+      What version do you find from clicking on "Code > About Visual Studio Code"?
+    placeholder: |
+      Example: Version: 1.89.1 (Universal)
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Salesforce Code Analyzer Extension Version
+    description: |
+      What version do you find from clicking "Code > Settings > Extensions > 'Salesforce Code Analyzer'"?
+    placeholder: |
+      Example: v0.5.0
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Salesforce CLI Version
+    description: |
+      What do you get from typing the command "sf --version" in the terminal?
+    placeholder: |
+      Example: @salesforce/cli/2.40.7 darwin-arm64 node-v20.12.2
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Code Analyzer CLI Plugin (@salesforce/sfdx-scanner) Version
+    description: |
+      What do you get from typing the command "sf plugins" in the terminal?
+    placeholder: |
+      Example: @salesforce/sfdx-scanner 4.1.0 (latest-beta)
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Additional Context (Screenshots, Files, etc)
+    description: Add any other context about the problem.
+    placeholder: |
+      Drag any files or screenshots you have here.
+- type: textarea
+  attributes:
+    label: Workaround
+    description: What ways have you found to sidestep the problem? If you haven't found a workaround, what have you tried so far?
+- type: dropdown
+  attributes:
+    label: Urgency
+    description: What is the severity of the problem?
+    options:
+    - Low
+    - Moderate
+    - High
+    - Critical
+    default: 0
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/1-feature-request.yml

@@ -0,0 +1,44 @@
+name: Request a New Feature
+description: Request a new Salesforce Code Analyzer Extension feature.
+title: "[Feature Request] <YOUR_TITLE_HERE>"
+labels: ['USER STORY']
+body:
+- type: textarea
+  attributes:
+    label: Need/Problem Description
+    description: First provide a clear and concise description of what your need or problem is.
+    placeholder: When I do XYZ, I am unable to...
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe your Desired Solution
+    description: Provide a clear and concise description of the enhancement you would like to see added to Salesforce Code Analyzer Extension.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Alternatives Considered
+    description: Describe any alternative solutions or features you've considered.
+- type: textarea
+  attributes:
+    label: Additional Context (Screenshots, Files, etc)
+    description: Add any other context about the problem.
+    placeholder: |
+      Drag any files or screenshots you have here.
+- type: textarea
+  attributes:
+    label: Workaround
+    description: What ways have you found to sidestep the problem? If you haven't found a workaround, what have you tried so far?
+- type: dropdown
+  attributes:
+    label: Urgency
+    description: What is the severity of the problem?
+    options:
+    - Low
+    - Moderate
+    - High
+    - Critical
+    default: 0
+  validations:
+    required: true

.github/workflows/create-github-release.yml

@@ -0,0 +1,60 @@
+name: create-github-release
+on:
+  pull_request:
+    branches:
+      - main
+    types:
+      # There's no event type for "merged", so we just run any time a PR is closed, and exit early
+      # if the PR wasn't actually merged.
+      - closed
+
+jobs:
+  verify-should-run:
+    # Since the workflow runs any time a PR against main is closed, we need this
+    # `if` to make sure that the workflow only does anything meaningful if the PR
+    # was actually merged.
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo 'PR was merged, so running is fine'
+  # We need a VSIX to attach to the release.
+  create-vsix-artifact:
+    name: 'Upload VSIX as artifact'
+    needs: verify-should-run
+    uses: ./.github/workflows/create-vsix-artifact.yml
+  create-github-release:
+    runs-on: ubuntu-latest
+    needs: create-vsix-artifact
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout main
+        uses: actions/checkout@v4
+        with:
+          ref: main
+      - name: Get version property
+        id: get-version-property
+        run: |
+          PACKAGE_VERSION=$(jq -r ".version" package.json)
+          echo "package_version=$PACKAGE_VERSION" >> "$GITHUB_OUTPUT"
+      - name: Download VSIX artifact
+        id: download
+        uses: actions/download-artifact@v4
+        with:
+          name: vsix
+          # Download the VSIX to a subdirectory of HOME, so it's guaranteed to be somewhere we can see.
+          path: ~/downloads/vsix
+      # The VSIX is zipped. Unzip it.
+      - run: unzip ~/downloads/vsix
+      # Create the release
+      - name: Create github release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ steps.get-version-property.outputs.package_version }}
+          name: v${{ steps.get-version-property.outputs.package_version }}
+          body: See [release notes](https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/release-notes.html)
+          target_commitish: main
+          token: ${{ secrets.SVC_CLI_BOT_GITHUB_TOKEN }}
+          make_latest: true
+          # Attach the unzipped VSIX using a glob
+          files: ~/downloads/*.vsix