fix: use CONTINUE_APP_ID and CONTINUE_APP_PRIVATE_KEY secrets

- Both app-id and app-private-key are now passed as secrets
- Removed default app-id value
- Updated test workflow to use proper secret names
- Users need to set CONTINUE_APP_ID and CONTINUE_APP_PRIVATE_KEY in their repo secrets

Author: bdougie

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

@@ -18,14 +18,8 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      # Example 1: Basic usage (no GitHub App - uses default token)
       - uses: continuedev/continue/actions/base-review@bdougie/continue-agent
         with:
           continue-api-key: ${{ secrets.CONTINUE_API_KEY }}
-      
-      # Example 2: With GitHub App (if you have your own app)
-      # - uses: continuedev/continue/actions/base-review@bdougie/continue-agent
-      #   with:
-      #     continue-api-key: ${{ secrets.CONTINUE_API_KEY }}
-      #     app-id: ${{ vars.MY_APP_ID }}
-      #     app-private-key: ${{ secrets.MY_APP_PRIVATE_KEY }}
+          app-id: ${{ secrets.CONTINUE_APP_ID }}
+          app-private-key: ${{ secrets.CONTINUE_APP_PRIVATE_KEY }}

actions/base-review/action.yml

@@ -7,11 +7,10 @@ inputs:
     description: "API key for Continue service (required)"
     required: true
   app-id:
-    description: "GitHub App ID (optional, defaults to Continue's app)"
+    description: "GitHub App ID (optional)"
     required: false
-    default: "1090372"  # Continue Agent App ID
   app-private-key:
-    description: "GitHub App Private Key (optional, defaults to Continue's app)"
+    description: "GitHub App Private Key (optional)"
     required: false
 
 runs: