Fix bot workflow upgrading lock file and remove docdict and stubs

[mscheltienne]

Summary by CodeRabbit

• Chores
  • Updated the workflow name and expanded triggers to include scheduled and manual runs.
  • Improved permissions handling and job configurations for automation tasks.
  • Enhanced automation steps for updating and upgrading dependencies.
  • Refined auto-merge conditions for pull requests.

[coderabbitai]

Warning

Rate limit exceeded

@mscheltienne has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between aaa7177 and 66b0077.

📒 Files selected for processing (23)

• .github/labeler.yaml (0 hunks)
• .github/workflows/auto-label.yaml (0 hunks)
• .github/workflows/bot.yaml (1 hunks)
• .github/workflows/stubs.yaml (0 hunks)
• README.md (0 hunks)
• template/__init__.pyi (0 hunks)
• template/_commands/tests/test_main.py (1 hunks)
• template/_commands/tests/test_sys_info.py (1 hunks)
• template/utils/__init__.pyi (0 hunks)
• template/utils/_checks.py (1 hunks)
• template/utils/_checks.pyi (0 hunks)
• template/utils/_docs.py (0 hunks)
• template/utils/_docs.pyi (0 hunks)
• template/utils/_fixes.pyi (0 hunks)
• template/utils/_imports.pyi (0 hunks)
• template/utils/config.pyi (0 hunks)
• template/utils/logs.py (3 hunks)
• template/utils/logs.pyi (0 hunks)
• template/utils/tests/test_checks.py (7 hunks)
• template/utils/tests/test_docs.py (2 hunks)
• template/utils/tests/test_imports.py (1 hunks)
• template/utils/tests/test_logs.py (6 hunks)
• tools/stubgen.py (0 hunks)

Walkthrough

The GitHub Actions workflow configuration was updated to rename the workflow, expand trigger events, adjust permissions, and refine job steps for uv-lock and auto-merge. Conditional logic and commit procedures were revised, with improved handling for scheduled and manual runs, and permissions were specified at the job level.

Changes

File(s)	Change Summary
.github/workflows/bot.yaml	Renamed workflow, updated triggers, moved permissions to jobs, revised job steps and conditions.

Poem

In the garden of code where workflows grow,
A bunny hops where triggers now flow.
With schedules and merges, permissions anew,
The garden’s more tidy, the chores fewer too!
At dawn’s gentle hour, the bot hops with glee—
“Upgrade uv.lock!”—a carrot for me! 🥕

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/bot.yaml (1)

39-39: Consider parameterizing repository check
Hard-coding github.repository == 'mscheltienne/template-python' may limit reusability in forks or new repos—consider making it configurable or removing it.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67d9b11 and aaa7177.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• .github/workflows/bot.yaml (1 hunks)

🔇 Additional comments (6)

.github/workflows/bot.yaml (6)

1-1: Workflow renamed to autofix.ci
The new name accurately reflects its purpose and aligns with other CI workflows.

---

6-9: Expanded trigger events look good
Including schedule and workflow_dispatch alongside pull_request increases automation flexibility.

---

13-14: Scoped contents: write permission to uv-lock job
Moving permissions to the job level adheres to the principle of least privilege.

---

20-21: Pin autofix-ci/action@v1.3.2 for PR runs
Locking to a specific action version and restricting it to pull requests ensures stability and security.

---

25-31: Push step for scheduled/manual runs is correct
The conditional commit & push only when changes exist avoids no-op commits and keeps the history clean.

---

35-37: Scoped permissions for auto-merge job
Granting only contents: write and pull-requests: write to this job follows best practices.