Update prek_autoupdate.yml

[Snuffy2]

Summary by CodeRabbit

• Chores
  • Updated automated maintenance workflow scheduling.
  • Added automatic runs when changes are pushed to the main branch.
  • Simplified the workflow’s update configuration.

Greptile Summary

This PR changes when prek autoupdate runs and stops explicitly dispatching downstream validation workflows.

• Changes the scheduled run from 06:19 UTC to 04:00 UTC daily.
• Adds a push trigger for the main branch.
• Removes actions:write permission and dispatches for documentation, lint, and pytest coverage workflows.

Confidence Score: 3/5

This PR should not merge until pytest coverage remains enabled for bot-authored autoupdate pull requests.

Removing the explicit workflow dispatch means the coverage workflow falls back to a pull-request path whose job condition deliberately skips bot and dependency pull requests.

Files Needing Attention: .github/workflows/prek_autoupdate.yml, .github/workflows/pytest_coverage.yml

Important Files Changed

Filename	Overview
.github/workflows/prek_autoupdate.yml	The trigger changes are straightforward, but removing downstream dispatches leaves bot-authored autoupdate pull requests without pytest coverage validation.

Prompt To Fix All With AI

### Issue 1
.github/workflows/prek_autoupdate.yml:14-17
**Coverage validation no longer runs**

When prek-autoupdate creates a bot-authored pull request, removing `dispatch-workflows` leaves `pytest_coverage.yml` reachable only through its pull-request trigger, whose job condition skips bot and dependency pull requests, causing the generated update to receive no pytest coverage validation.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Update prek_autoupdate.yml" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[coderabbitai]

📝 Walkthrough

Walkthrough

The workflow schedule was changed, pushes to main were added as a trigger, and the reusable prek-autoupdate call was reduced to the update-day input.

Changes

Pre-commit Autoupdate

Layer / File(s)	Summary
Workflow triggers and reusable inputs .github/workflows/prek_autoupdate.yml	The schedule now runs at 0 4 * * *, pushes to main trigger the workflow, and the previous dispatch-workflows input was removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the changed workflow file and is specific enough to identify the main update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/prek_autoupdate.yml (1)

17-18: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Run post-PR validation on generated update branches.

The auto-update PR is created by GITHUB_TOKEN, so the downstream pull-request workflows (docs, linters, pytest_coverage) don’t run automatically. Without dispatch-workflows, each update branch bypasses these gates unless an approver manually runs them. Add back the reusable workflow input and the caller’s actions: write permission, or explicitly remove/deprecate these checks for generated branches.

Suggested restoration

     permissions:
       contents: write
       pull-requests: write
+      actions: write
     with:
       update-day: "6"
+      dispatch-workflows: |
+        docs.yml
+        linters.yml
+        pytest_coverage.yml

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/prek_autoupdate.yml around lines 17 - 18, Restore the
reusable workflow input for dispatching downstream workflows in the auto-update
job alongside update-day, and grant the caller actions: write permission. Use
the existing workflow’s dispatch-workflows configuration so generated update
branches trigger docs, linters, and pytest_coverage validation.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In @.github/workflows/prek_autoupdate.yml:
- Around line 17-18: Restore the reusable workflow input for dispatching
downstream workflows in the auto-update job alongside update-day, and grant the
caller actions: write permission. Use the existing workflow’s dispatch-workflows
configuration so generated update branches trigger docs, linters, and
pytest_coverage validation.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f27f42c7-a52a-4ba7-9351-0dbbfd2df443

📥 Commits

Reviewing files that changed from the base of the PR and between 5a08b56 and 55b2043.

📒 Files selected for processing (1)

• .github/workflows/prek_autoupdate.yml

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 55b20434a4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".