Use DEPLOY_TOKEN for checkout to trigger deploy workflow
Some checks failed
Deploy Site / deploy-chirho (push) Failing after 10s

This commit is contained in:
2026-01-12 20:36:19 +00:00
parent 9d39391757
commit 32232fb6cd

View File

@@ -1,4 +1,3 @@
# For God so loved the world — John 3:16
name: Claude Edit Workflow name: Claude Edit Workflow
on: on:
@@ -9,46 +8,50 @@ on:
jobs: jobs:
edit-chirho: edit-chirho:
runs-on: claude-chirho # Only run if: has edit-request label AND (is issue event OR comment is NOT from bot)
if: | if: |
contains(github.event.issue.labels.*.name, 'edit-request-chirho') && contains(github.event.issue.labels.*.name, 'edit-request-chirho') &&
(github.event_name == 'issues' || github.event.comment.user.login != 'claude-bot-chirho') (github.event_name == 'issues' || github.event.comment.user.login != 'claude-bot-chirho')
runs-on: claude-chirho
steps: steps:
- name: Checkout repository - name: Checkout repository
uses: actions/checkout@v4 uses: actions/checkout@v4
with: with:
fetch-depth: 0 fetch-depth: 0
token: ${{ secrets.DEPLOY_TOKEN }}
- name: Run Claude Code - name: Run Claude Code
uses: anthropics/claude-code-action@v1
with:
mcp_config: .gitea/mcp-gitea-config-chirho.json
allowed_tools: Read,Write,Edit,Glob,Grep,gitea_get_issue_thread_chirho,gitea_add_issue_comment_chirho
prompt: |
You are editing a customer website based on their feedback.
1. Use gitea_get_issue_thread_chirho to read the full issue thread
2. Find the most recent message from the site owner
3. If the owner is requesting new edits, make those changes to the site files
4. If you made changes, use gitea_add_issue_comment_chirho to post a summary
5. If the owner's last message was already addressed, skip
Focus on making clean, minimal edits that match the existing code style.
Follow the _chirho naming convention for any new identifiers.
env: env:
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY_CHIRHO }} ISSUE_NUMBER: ${{ github.event.issue.number }}
GITEA_TOKEN: ${{ secrets.GITEA_TOKEN_CHIRHO }} ISSUE_TITLE: ${{ github.event.issue.title }}
run: |
cd $GITHUB_WORKSPACE
git config user.email "claude-bot@perffection.com"
git config user.name "Claude Bot"
cat << PROMPT_EOF | ~/.local/bin/claude -p --verbose --output-format stream-json --mcp-config ~/mcp-gitea-config-chirho.json --allowedTools "Read,Write,Edit,Glob,Grep,Bash,mcp__gitea-chirho__*"
You are editing a customer website based on feedback.
Issue number ${ISSUE_NUMBER}: ${ISSUE_TITLE}
IMPORTANT: First use gitea_get_issue_thread_chirho to read the full conversation history.
After reading the thread:
1. Look at the LATEST message from the site owner (not from claude-bot-chirho)
2. If there is a new request, make the edits
3. Post a brief comment summarizing what you did
4. If the latest owner message has already been addressed, do nothing
Working directory contains the site files. Make changes directly.
DO NOT run git commands - the workflow will handle committing changes.
PROMPT_EOF
- name: Commit and push changes - name: Commit and push changes
run: | run: |
git config user.name "Claude Bot" cd $GITHUB_WORKSPACE
git config user.email "claude-bot-chirho@perffection.com"
git add -A git add -A
if git diff --staged --quiet; then if git diff --staged --quiet; then
echo "No changes to commit" echo "No changes to commit"
else else
git commit -m "${{ github.event.issue.title }}" git commit -m "Edit: ${{ github.event.issue.title }}"
git push git push
fi fi
# JESUS CHRIST IS LORD