Walkthrough

Adds a new GitHub Actions workflow that runs on pushes to Lib/** or manual dispatch, clones RustPython and CPython with sparse-checkout, runs a Python-based scripts/update_lib todo update, and edits a specified GitHub issue with the generated body.

Changes

Sequence Diagram(s)

sequenceDiagram
  participant Trigger as GitHub Event
  participant Actions as GitHub Actions
  participant RP as RustPython Repo
  participant CP as CPython Repo
  participant Script as update_lib (Python)
  participant API as GitHub Issues API

  Trigger->>Actions: push to main (Lib/**) / workflow_dispatch
  Actions->>RP: sparse checkout RustPython (clone subset)
  Actions->>CP: sparse checkout CPython (clone subset)
  Actions->>Script: run `scripts/update_lib todo` (env: PY_VER, ISSUE_ID)
  Script->>Actions: output body.txt
  Actions->>API: edit issue (ISSUE_ID) with body.txt
  API-->>Actions: confirm issue updated

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 I hopped through repos, clipped and neat,
Wrote a body, ran the script on repeat,
An issue updated with a cheerful thump—
Libraries tracked with a joyful jump! ✨

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

.github/workflows/update-libs-status.yaml (3)

9-9: Consider adding workflow_dispatch inputs for flexibility.

The linked issue (#7061) mentions supporting configurable target issue ID and CPython version as workflow inputs. Adding optional inputs with defaults matching the current env vars would let maintainers trigger ad-hoc runs against a different issue or version without a code change.

Suggested change

   workflow_dispatch:
+    inputs:
+      python_version:
+        description: "CPython tag to compare against"
+        required: false
+        default: "v3.14.3"
+      issue_id:
+        description: "GitHub issue number to update"
+        required: false
+        default: "6839"

Then reference them as:

env:
  PYTHON_VERSION: ${{ inputs.python_version || 'v3.14.3' }}
  ISSUE_ID: ${{ inputs.issue_id || '6839' }}

---

43-47: Timezone is implicit — fine for display, just noting it's UTC.

GitHub Actions runners default to UTC. If the displayed timestamp should be explicit, you could use date -u or append UTC, but this is a nit.

---

81-82: No setup-python action — relies on system Python.

The ubuntu-latest runner ships Python 3.x, but its version can change when GitHub updates the image. If scripts/update_lib requires a specific minimum Python version or you want reproducibility, consider adding actions/setup-python. Otherwise this is fine for simplicity. Based on learnings, the maintainer prefers keeping workflows simple.

• X
• Mastodon
• Reddit
• LinkedIn