Skip to content

Commit c9bb32b

Browse files
PDowneyPDowney
authored
Workflow fixes
1 parent b0eff56 commit c9bb32b

1 file changed

Lines changed: 24 additions & 71 deletions

File tree

‎.github/workflows/gemini-issue-assistant.yml‎

Lines changed: 24 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -148,19 +148,10 @@ jobs:
148148
EVENT_NAME: ${{ github.event_name }}
149149
ISSUE_TITLE: ${{ github.event.issue.title }}
150150
ISSUE_AUTHOR: ${{ github.event.issue.user.login }}
151-
COMMENT_AUTHOR: ${{ github.event.comment.user.login }}
152151
run: |
153-
if [ "$EVENT_NAME" = "issues" ]; then
154-
echo "type=issue-analysis" >> $GITHUB_OUTPUT
155-
echo "Issue: $ISSUE_TITLE"
156-
echo "Author: $ISSUE_AUTHOR"
157-
elif [ "$EVENT_NAME" = "issue_comment" ]; then
158-
echo "type=comment-analysis" >> $GITHUB_OUTPUT
159-
echo "Comment on issue: $ISSUE_TITLE"
160-
echo "Comment author: $COMMENT_AUTHOR"
161-
else
162-
echo "type=skip" >> $GITHUB_OUTPUT
163-
fi
152+
echo "type=issue-analysis" >> $GITHUB_OUTPUT
153+
echo "Issue: $ISSUE_TITLE"
154+
echo "Author: $ISSUE_AUTHOR"
164155
165156
- name: Scan Codebase for Context
166157
id: scan-code
@@ -237,64 +228,32 @@ jobs:
237228
238229
- name: Create analysis prompt
239230
env:
240-
ANALYSIS_TYPE: ${{ steps.analysis-type.outputs.type }}
241231
ISSUE_TITLE: ${{ github.event.issue.title }}
242232
ISSUE_BODY: ${{ github.event.issue.body }}
243233
ISSUE_AUTHOR: ${{ github.event.issue.user.login }}
244-
COMMENT_BODY: ${{ github.event.comment.body }}
245-
COMMENT_AUTHOR: ${{ github.event.comment.user.login }}
246234
CONTEXT_AVAILABLE: ${{ steps.scan-code.outputs.context-available }}
247235
run: |
248-
# Skip analysis if not relevant
249-
if [ "$ANALYSIS_TYPE" = "skip" ]; then
250-
echo "No relevant issue activity. Skipping analysis." > analysis_prompt.txt
251-
echo "analysis-skipped=true" >> $GITHUB_OUTPUT
252-
exit 0
253-
elif [ "$ANALYSIS_TYPE" = "issue-analysis" ]; then
254-
# Create issue-focused prompt - FOCUS ON USER'S PROBLEM FIRST
255-
echo "You are an expert Linux system administrator and LEMP stack automation specialist helping users solve server configuration problems." > analysis_prompt.txt
256-
echo "" >> analysis_prompt.txt
257-
echo "CRITICAL INSTRUCTION: FOCUS FIRST ON UNDERSTANDING THE USER'S ISSUE." >> analysis_prompt.txt
258-
echo "Then scan the codebase to find potential solutions or identify configuration-related causes." >> analysis_prompt.txt
259-
echo "" >> analysis_prompt.txt
260-
echo "ISSUE DETAILS:" >> analysis_prompt.txt
261-
echo "Title: $ISSUE_TITLE" >> analysis_prompt.txt
262-
echo "Author: @$ISSUE_AUTHOR" >> analysis_prompt.txt
263-
echo "Description:" >> analysis_prompt.txt
264-
echo "$ISSUE_BODY" >> analysis_prompt.txt
265-
echo "" >> analysis_prompt.txt
266-
echo "ANALYSIS APPROACH:" >> analysis_prompt.txt
267-
echo "1. Understand the server administration problem/request thoroughly" >> analysis_prompt.txt
268-
echo "2. Scan the bash scripts and configuration files for related functionality" >> analysis_prompt.txt
269-
echo "3. Identify potential configuration-based solutions or fixes" >> analysis_prompt.txt
270-
echo "4. Check for existing similar server automation functionality" >> analysis_prompt.txt
271-
echo "5. Provide actionable system administration recommendations" >> analysis_prompt.txt
272-
echo "" >> analysis_prompt.txt
273-
echo "REPOSITORY CONTEXT: EngineScript LEMP server automation (Ubuntu 24.04 LTS, Nginx, PHP 8.4+, MariaDB 11.8+, Redis, Cloudflare integration)" >> analysis_prompt.txt
274-
echo "" >> analysis_prompt.txt
275-
elif [ "$ANALYSIS_TYPE" = "comment-analysis" ]; then
276-
# Create comment-focused prompt - FOCUS ON CONVERSATION CONTEXT
277-
echo "You are an expert Linux system administrator and LEMP stack automation specialist analyzing a server configuration discussion." > analysis_prompt.txt
278-
echo "" >> analysis_prompt.txt
279-
echo "CRITICAL INSTRUCTION: FOCUS ON THE CONVERSATION CONTEXT AND NEW INFORMATION." >> analysis_prompt.txt
280-
echo "Analyze the new comment in relation to the original server administration issue and provide relevant insights." >> analysis_prompt.txt
281-
echo "" >> analysis_prompt.txt
282-
echo "ORIGINAL ISSUE:" >> analysis_prompt.txt
283-
echo "Title: $ISSUE_TITLE" >> analysis_prompt.txt
284-
echo "Description: $ISSUE_BODY" >> analysis_prompt.txt
285-
echo "" >> analysis_prompt.txt
286-
echo "NEW COMMENT:" >> analysis_prompt.txt
287-
echo "Author: @$COMMENT_AUTHOR" >> analysis_prompt.txt
288-
echo "Content: $COMMENT_BODY" >> analysis_prompt.txt
289-
echo "" >> analysis_prompt.txt
290-
echo "ANALYSIS FOCUS:" >> analysis_prompt.txt
291-
echo "1. How does this comment relate to the original server configuration issue?" >> analysis_prompt.txt
292-
echo "2. What new server administration information or clarification is provided?" >> analysis_prompt.txt
293-
echo "3. Are there bash script or configuration file implications from this comment?" >> analysis_prompt.txt
294-
echo "4. What follow-up server administration actions are suggested?" >> analysis_prompt.txt
295-
echo "" >> analysis_prompt.txt
296-
echo "REPOSITORY CONTEXT: EngineScript LEMP server automation (Ubuntu 24.04 LTS, Nginx, PHP 8.4+, MariaDB 11.8+, Redis, Cloudflare integration)" >> analysis_prompt.txt
297-
fi
236+
# Create issue-focused prompt - FOCUS ON USER'S PROBLEM FIRST
237+
echo "You are an expert Linux system administrator and LEMP stack automation specialist helping users solve server configuration problems." > analysis_prompt.txt
238+
echo "" >> analysis_prompt.txt
239+
echo "CRITICAL INSTRUCTION: FOCUS FIRST ON UNDERSTANDING THE USER'S ISSUE." >> analysis_prompt.txt
240+
echo "Then scan the codebase to find potential solutions or identify configuration-related causes." >> analysis_prompt.txt
241+
echo "" >> analysis_prompt.txt
242+
echo "ISSUE DETAILS:" >> analysis_prompt.txt
243+
echo "Title: $ISSUE_TITLE" >> analysis_prompt.txt
244+
echo "Author: @$ISSUE_AUTHOR" >> analysis_prompt.txt
245+
echo "Description:" >> analysis_prompt.txt
246+
echo "$ISSUE_BODY" >> analysis_prompt.txt
247+
echo "" >> analysis_prompt.txt
248+
echo "ANALYSIS APPROACH:" >> analysis_prompt.txt
249+
echo "1. Understand the server administration problem/request thoroughly" >> analysis_prompt.txt
250+
echo "2. Scan the bash scripts and configuration files for related functionality" >> analysis_prompt.txt
251+
echo "3. Identify potential configuration-based solutions or fixes" >> analysis_prompt.txt
252+
echo "4. Check for existing similar server automation functionality" >> analysis_prompt.txt
253+
echo "5. Provide actionable system administration recommendations" >> analysis_prompt.txt
254+
echo "" >> analysis_prompt.txt
255+
echo "REPOSITORY CONTEXT: EngineScript LEMP server automation (Ubuntu 24.04 LTS, Nginx, PHP 8.4+, MariaDB 11.8+, Redis, Cloudflare integration)" >> analysis_prompt.txt
256+
echo "" >> analysis_prompt.txt
298257
299258
# Add codebase context if available
300259
if [ "$CONTEXT_AVAILABLE" = "true" ]; then
@@ -314,13 +273,7 @@ jobs:
314273
id: ai-analysis
315274
env:
316275
GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
317-
ANALYSIS_SKIPPED: ${{ steps.analysis-type.outputs.analysis-skipped }}
318276
run: |
319-
if [ "$ANALYSIS_SKIPPED" = "true" ]; then
320-
echo "Analysis skipped"
321-
exit 0
322-
fi
323-
324277
echo "🤖 Starting AI issue analysis with official Google SDK..."
325278
echo "📝 Prompt file size: $(wc -c < analysis_prompt.txt) bytes"
326279
echo "🔑 API key status: $([ -n "$GEMINI_API_KEY" ] && echo "✅ Set" || echo "❌ Missing")"

0 commit comments

Comments
 (0)