Merge branch 'main' into parallel-edit

Author: uinstinct

.github/ISSUE_TEMPLATE/config.yml

@@ -6,6 +6,3 @@ contact_links:
   - name: Have a question?
     url: https://github.com/continuedev/continue/discussions
     about: Search for existing questions or ask a new one
-  - name: Something else? Join the Continue Community
-    url: https://discord.gg/vapESyrFmJ
-    about: Join our Discord to chat with our community

.github/actions/run-vscode-e2e-test/action.yml

@@ -17,6 +17,10 @@ inputs:
     description: "Whether this is a fork (affects SSH tests)"
     required: false
     default: "false"
+  github_token:
+    description: "GitHub token for authenticated API requests (e.g., @vscode/ripgrep download)"
+    required: false
+    default: ""
 
 runs:
   using: "composite"
@@ -64,6 +68,8 @@ runs:
           cd core
           npm ci
         fi
+      env:
+        GITHUB_TOKEN: ${{ inputs.github_token }}
 
     - name: Fix VSCode binary permissions
       shell: bash

.github/workflows/compliance.yaml

@@ -329,6 +329,7 @@ jobs:
           ssh_key: ${{ secrets.GH_ACTIONS_SSH_TEST_KEY_PEM }}
           ssh_host: ${{ secrets.GH_ACTIONS_SSH_TEST_DNS_NAME }}
           is_fork: ${{ github.event.pull_request.head.repo.fork == true || github.actor == 'dependabot[bot]' }}
+          github_token: ${{ secrets.CI_GITHUB_TOKEN }}
 
   jetbrains-tests:
     runs-on: ubuntu-latest

.github/workflows/continue-general-review.yaml

@@ -48,4 +48,4 @@ jobs:
             -H "Authorization: Bearer $CONTINUE_API_KEY" \
             -d "$json_body")
           id=$(echo $response | jq -r '.id')
-          echo "https://hub.continue.dev/hub?type=agents/$id"
+          echo "https://continue.dev/hub?type=agents/$id"

.github/workflows/pr-checks.yaml

@@ -220,39 +220,47 @@ jobs:
           gh release edit "v${{ steps.find_beta.outputs.beta_version }}" \
             --notes "This beta version has been promoted to stable as v${{ steps.final_version.outputs.stable_version }}."
 
-      - name: Publish Blueprint to Runloop
+      - name: Publish Blueprints to Runloop
         env:
           RUNLOOP_API_KEY: ${{ secrets.RUNLOOP_API_KEY }}
         run: |
-          echo "Publishing blueprint 'cn' to Runloop API for version ${{ steps.final_version.outputs.stable_version }}"
-
-          # Use blueprint configuration from template file
-          cp .github/workflows/runloop-blueprint-template.json blueprint.json
-
-          # Publish to Runloop API
-          response=$(curl -X POST "https://api.runloop.ai/v1/blueprints" \
-            -H "Authorization: Bearer $RUNLOOP_API_KEY" \
-            -H "Content-Type: application/json" \
-            -d @blueprint.json \
-            -w "%{http_code}" \
-            -s)
-
-          http_code=$(echo "$response" | tail -c 4)
-          response_body=$(echo "$response" | head -c -4)
-
-          if [[ "$http_code" == "200" ]] || [[ "$http_code" == "201" ]]; then
-            echo "✅ Successfully published blueprint to Runloop API"
-            echo "Response: $response_body"
-            
-            # Extract blueprint ID if available
-            blueprint_id=$(echo "$response_body" | jq -r '.id // empty')
-            if [[ -n "$blueprint_id" ]]; then
-              echo "Blueprint ID: $blueprint_id"
-              echo "blueprint_id=$blueprint_id" >> $GITHUB_OUTPUT
+          publish_blueprint() {
+            local name=$1
+            local template=$2
+
+            echo "Publishing blueprint '$name' to Runloop API for version ${{ steps.final_version.outputs.stable_version }}"
+
+            # Use blueprint configuration from template file
+            cp ".github/workflows/$template" blueprint.json
+
+            # Publish to Runloop API
+            response=$(curl -X POST "https://api.runloop.ai/v1/blueprints" \
+              -H "Authorization: Bearer $RUNLOOP_API_KEY" \
+              -H "Content-Type: application/json" \
+              -d @blueprint.json \
+              -w "%{http_code}" \
+              -s)
+
+            http_code=$(echo "$response" | tail -c 4)
+            response_body=$(echo "$response" | head -c -4)
+
+            if [[ "$http_code" == "200" ]] || [[ "$http_code" == "201" ]]; then
+              echo "✅ Successfully published blueprint '$name' to Runloop API"
+              echo "Response: $response_body"
+
+              # Extract blueprint ID if available
+              blueprint_id=$(echo "$response_body" | jq -r '.id // empty')
+              if [[ -n "$blueprint_id" ]]; then
+                echo "Blueprint ID: $blueprint_id"
+              fi
+            else
+              echo "❌ Failed to publish blueprint '$name' to Runloop API"
+              echo "HTTP Code: $http_code"
+              echo "Response: $response_body"
+              exit 1
             fi
-          else
-            echo "❌ Failed to publish blueprint to Runloop API"
-            echo "HTTP Code: $http_code"
-            echo "Response: $response_body"
-            exit 1
-          fi
+          }
+
+          # Publish both cn and cn-staging blueprints
+          publish_blueprint "cn" "runloop-blueprint-template.json"
+          publish_blueprint "cn-staging" "runloop-blueprint-staging-template.json"

.github/workflows/run-continue-agent.yml

@@ -65,7 +65,7 @@ an enhancement are:
   - If not, [create an issue](https://github.com/continuedev/continue/issues)
   - Please describe the enhancement in as much detail as you can, and why it would be useful
 
-- Join the [Continue Discord](https://discord.gg/NWtdYexhMs) and tell us about your idea in the `#feedback` channel
+- Join the [GitHub Discussions](https://github.com/continuedev/continue/discussions) and tell us about your idea
 
 ## 📖 Updating / Improving Documentation
 
@@ -91,7 +91,7 @@ You can run the documentation server locally using either of the following metho
 3. Run the following command to start the documentation server:
 
    ```bash
-   npm run start
+   npm run dev
    ```
 
 #### Method 2: VS Code Task
@@ -233,7 +233,7 @@ When contributing, please update or create the appropriate tests to help verify
 
 ### Getting Help
 
-Join [#contribute on Discord](https://discord.gg/vapESyrFmJ) to engage with maintainers and other contributors.
+Join the [GitHub Discussions](https://github.com/continuedev/continue/discussions) to engage with maintainers and other contributors.
 
 ## Contributing New LLM Providers/Models