handle multiple PRs with schema changes

2026-04-23 19:46:09 +02:00 · 2026-02-12 15:31:53 -05:00
parent 1694fe0b46
commit 9acffe1e56
2 changed files with 168 additions and 0 deletions
@@ -0,0 +1,100 @@
+name: Update Community PRs After Merge
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'community/**'
+      - 'schemas/community_submission.*.schema.json'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  update-open-prs:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies
+        run: pip install jsonschema
+
+      - name: Get current schema version
+        id: schema
+        run: |
+          # Find the latest schema version on main
+          latest=$(ls schemas/community_submission.v*.schema.json 2>/dev/null | sed 's/.*\.v\([0-9]*\)\.schema\.json/\1/' | sort -n | tail -1)
+          echo "latest_version=${latest:-1}" >> "$GITHUB_OUTPUT"
+          echo "Latest schema version: ${latest:-1}"
+
+      - name: Find and update open community PRs
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          LATEST_SCHEMA_VERSION: ${{ steps.schema.outputs.latest_version }}
+        run: |
+          # Get list of open community PRs
+          prs=$(gh pr list --label community --state open --json number,headRefName --jq '.[] | "\(.number) \(.headRefName)"')
+          
+          if [ -z "$prs" ]; then
+            echo "No open community PRs found"
+            exit 0
+          fi
+          
+          echo "$prs" | while read pr_number branch_name; do
+            echo "Processing PR #$pr_number (branch: $branch_name)"
+            
+            # Checkout PR branch
+            git fetch origin "$branch_name"
+            git checkout "$branch_name"
+            
+            # Check if this PR has a schema file that needs updating
+            pr_schema=$(ls schemas/community_submission.v*.schema.json 2>/dev/null | sed 's/.*\.v\([0-9]*\)\.schema\.json/\1/' | sort -n | tail -1)
+            
+            if [ "$pr_schema" -le "$LATEST_SCHEMA_VERSION" ] 2>/dev/null; then
+              echo "  PR schema version ($pr_schema) <= main version ($LATEST_SCHEMA_VERSION)"
+              
+              # Merge main into PR branch
+              git config user.name "github-actions[bot]"
+              git config user.email "github-actions[bot]@users.noreply.github.com"
+              
+              if git merge origin/main -m "Merge main to update schema baseline"; then
+                # Regenerate schema for this PR's submission
+                python -m src.contributions.regenerate_pr_schema || true
+                
+                # If there are changes, commit and push
+                if [ -n "$(git status --porcelain schemas/)" ]; then
+                  new_version=$((LATEST_SCHEMA_VERSION + 1))
+                  git add schemas/
+                  git commit -m "Update schema to v${new_version} (rebased on main)"
+                  git push origin "$branch_name"
+                  echo "  Updated PR #$pr_number with new schema"
+                else
+                  git push origin "$branch_name"
+                  echo "  Merged main into PR #$pr_number"
+                fi
+              else
+                echo "  Merge conflict in PR #$pr_number, adding comment"
+                gh pr comment "$pr_number" --body "⚠️ **Merge Conflict**
+
+Another community submission was merged and this PR has conflicts.
+
+A maintainer may need to:
+1. Close this PR
+2. Remove the \`approved\` label from the original issue
+3. Re-add the \`approved\` label to regenerate the PR"
+                git merge --abort
+              fi
+            fi
+            
+            git checkout main
+          done