📝 Add permissions needed for private repos

[khulnasoft-bot]

📝 Add permissions needed for private repos

Summary by Sourcery

Document required GitHub Actions permissions for using the action with private repositories, align bot git user configuration with the GitHub Actions bot identity, and update GitHub Actions dependencies to their latest major versions.

Enhancements:

• Set the git user.name and user.email to the canonical github-actions[bot] identity used by GitHub Actions.

CI:

• Bump actions/checkout to v6 in the latest-changes workflow.

Documentation:

• Document the pull-requests: read permission requirement in README workflow examples for private repositories.
• Update the Latest Changes section in the README with recent dependency and feature changes, including bot configuration updates.

Tests:

• Update CI workflow actions (checkout, cache, upload-artifact) to the latest major versions in the test workflow.

Summary by CodeRabbit

• Chores

  • Upgraded CI workflow actions to their latest versions.
  • Updated automated bot identity used by release automation.

• Documentation

  • Added job-level permissions for workflows (including pull-requests: read).
  • Expanded release notes and workflow examples to reflect the above updates.

[sourcery-ai]

Reviewer's Guide

Documents and configures the GitHub Action to work correctly with private repositories, aligns the README examples with required permissions, bumps several GitHub Actions to their latest major versions, and updates the bot git identity used when committing latest changes.

Sequence diagram for latest-changes workflow with private repo permissions

sequenceDiagram
    actor Developer
    participant GitHubActions
    participant Job_latest_changes
    participant actions_checkout
    participant latest_changes_action
    participant GitHubAPI
    participant Git

    Developer->>GitHubActions: Push to default branch / trigger workflow
    GitHubActions->>Job_latest_changes: Start job latest-changes
    Job_latest_changes->>Job_latest_changes: permissions pull-requests read

    Job_latest_changes->>actions_checkout: Run actions/checkout@v6
    actions_checkout-->>Job_latest_changes: Repository checked out

    Job_latest_changes->>latest_changes_action: Run khulnasoft/latest-changes
    latest_changes_action->>GitHubAPI: List pull requests (requires pull-requests read)
    GitHubAPI-->>latest_changes_action: Pull request data

    latest_changes_action->>Git: git config user.name github-actions[bot]
    latest_changes_action->>Git: git config user.email github-actions[bot]@users.noreply.github.com
    latest_changes_action->>Git: Commit latest changes
    latest_changes_action->>GitHubAPI: Push commit to repository
    GitHubAPI-->>Developer: Latest changes available in repository

Loading

File-Level Changes

Change	Details	Files
Document and configure required GitHub Actions permissions for private repositories.	Add a permissions block with pull-requests: read to README workflow examples so users can run the action in private repos Annotate the permissions block with a comment explaining it is needed for private repositories	README.md
Update release notes / changelog section in README to reflect recent dependency PRs and this permissions change.	Add entries describing dependency bumps for actions/checkout, actions/cache, and actions/upload-artifact Add an entry describing this PR under the latest changes list Introduce a new Features subsection and note the bot user configuration update there	README.md
Bump GitHub Actions used in CI to newer major versions.	Update actions/checkout from v5 to v6 in test workflow Update actions/cache from v4 to v5 in test workflow Update actions/upload-artifact from v5 to v6 in test workflow Update actions/checkout from v5 to v6 in the latest-changes workflow	.github/workflows/test.yml .github/workflows/latest-changes.yml
Align the git author configuration with the GitHub Actions bot identity.	Change configured git user.name from github-actions to github-actions[bot] Change configured git user.email to github-actions[bot]@users.noreply.github.com to match the bot account	latest_changes/main.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@khulnasoft-bot has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 47 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 5 minutes and 47 seconds.

⌛ 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ecdaf3ea-4e72-4302-a7e9-49b8842947cf

📥 Commits

Reviewing files that changed from the base of the PR and between 3c3354f and 82c5656.

📒 Files selected for processing (1)

• latest_changes/model.py

Walkthrough

Updates GitHub Actions action versions, adds job-level workflow permissions for pull request access in examples, adjusts Git bot commit identity in the automation script, and records these changes in README release notes.

Changes

Cohort / File(s)	Summary
Workflow: single-version bump \.github/workflows/latest-changes.yml	Bumped actions/checkout from v5 → v6. No other workflow logic changed.
Workflows: multi-action bumps \.github/workflows/test.yml	Updated action versions: actions/checkout v5→v6, actions/cache v4→v5, actions/upload-artifact v5→v6.
Documentation / Examples README.md	Added job-level permissions: pull-requests: read to multiple workflow examples and updated release notes to list the action version bumps and new permission requirement.
Automation script latest_changes/main.py	Switched git config to use git_bin variable and changed commit identity from github-actions / github-actions@github.com to github-actions[bot] / github-actions[bot]@users.noreply.github.com.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Bot Bunny
I hop through commits with a cheery trot,
github-actions[bot] leaves a tidy spot,
Versions climb and permissions sing,
Pipelines hum — I bound and spring,
A carrot for CI, a celebratory hop! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title mentions adding permissions for private repos, which aligns with the core documentation and permission changes in README and workflows, but doesn't fully capture all substantive changes like git user configuration updates and GitHub Actions version bumps across multiple workflows.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• For the updated GitHub Actions git user, consider using the standard bot noreply email format (e.g. 41898282+github-actions[bot]@users.noreply.github.com) so commits are correctly attributed to the github-actions[bot] account.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- For the updated GitHub Actions git user, consider using the standard bot noreply email format (e.g. `41898282+github-actions[bot]@users.noreply.github.com`) so commits are correctly attributed to the `github-actions[bot]` account.

## Individual Comments

### Comment 1
<location path=".github/workflows/latest-changes.yml" line_range="19" />
<code_context>
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v6
       - name: Dump GitHub context
         env:
</code_context>
<issue_to_address>
**issue (bug_risk):** The `actions/checkout@v6` tag may not exist and could cause the workflow to fail.

`actions/checkout` is currently published up to `v4` (with `v4.x.x` tags). Using `@v6` will fail with `Resource not found` until that version exists. Please pin to the latest available major (e.g., `@v4`) or a specific `v4.x.x` tag instead.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): The actions/checkout@v6 tag may not exist and could cause the workflow to fail.

actions/checkout is currently published up to v4 (with v4.x.x tags). Using @v6 will fail with Resource not found until that version exists. Please pin to the latest available major (e.g., @v4) or a specific v4.x.x tag instead.

[khulnasoft-bot]

Suggested change

	- uses: actions/checkout@v6
	- uses: actions/checkout@v6

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@latest_changes/main.py`:
- Around line 236-239: Resolve the git executable once using shutil.which at
module startup (e.g., assign git_cmd = shutil.which("git") and raise a clear
error if None), import shutil if not present, and then replace all
subprocess.run invocations that currently pass the bare "git" string with the
resolved git_cmd variable (apply to the six subprocess.run calls shown in
main.py such as the git config and other git operations). Ensure each subprocess
call builds its argument list starting with git_cmd instead of "git" so PATH
lookup is avoided.

In `@README.md`:
- Around line 329-332: Update the "How does it work?" section text to reflect
the new bot identity by replacing occurrences of "github-actions" and
"github-actions@github.com" with "github-actions[bot]" and
"github-actions[bot]@users.noreply.github.com" respectively (search for the "How
does it work?" heading and the lines describing commit authorship to locate the
text to change).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b9d58928-0b87-4238-a255-16c618b50be7

📥 Commits

Reviewing files that changed from the base of the PR and between 53eda31 and ec2822e.

📒 Files selected for processing (4)

• .github/workflows/latest-changes.yml
• .github/workflows/test.yml
• README.md
• latest_changes/main.py

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify all subprocess git invocations still use bare "git" and should be migrated.
rg -nP --type=py 'subprocess\.run\(\[\s*"git"' latest_changes/main.py

Repository: khulnasoft/latest-changes

Length of output: 479

---

Harden all git subprocess calls by resolving the executable path once.

The file contains 6 subprocess.run calls using bare "git" (lines 236, 247, 261, 264, 269, 270), which rely on PATH lookup and trigger Ruff S607. Resolve the executable path once at startup using shutil.which() and reuse it for all git invocations.

Suggested hardening approach

+import shutil
...
+    git_bin = shutil.which("git")
+    if not git_bin:
+        logging.error("`git` executable not found in PATH")
+        sys.exit(1)
+
     logging.info("Setting up GitHub Actions git user")
-    subprocess.run(["git", "config", "user.name", "github-actions[bot]"], check=True)
+    subprocess.run([git_bin, "config", "user.name", "github-actions[bot]"], check=True)
     subprocess.run(
-        ["git", "config", "user.email", "github-actions[bot]@users.noreply.github.com"], check=True
+        [git_bin, "config", "user.email", "github-actions[bot]@users.noreply.github.com"], check=True
     )

Apply the same pattern to remaining git calls at lines 247, 261, 264, 269, and 270.

🧰 Tools

🪛 Ruff (0.15.7)

[error] 236-236: Starting a process with a partial executable path

(S607)

---

[error] 238-238: Starting a process with a partial executable path

(S607)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@latest_changes/main.py` around lines 236 - 239, Resolve the git executable
once using shutil.which at module startup (e.g., assign git_cmd =
shutil.which("git") and raise a clear error if None), import shutil if not
present, and then replace all subprocess.run invocations that currently pass the
bare "git" string with the resolved git_cmd variable (apply to the six
subprocess.run calls shown in main.py such as the git config and other git
operations). Ensure each subprocess call builds its argument list starting with
git_cmd instead of "git" so PATH lookup is avoided.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Update README bot identity text to match this new release-note entry.

This section now documents the bot-user-config change, but the “How does it work?” section still says commits are authored as github-actions / github-actions@github.com. Please align that text with github-actions[bot] and github-actions[bot]@users.noreply.github.com.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 329 - 332, Update the "How does it work?" section
text to reflect the new bot identity by replacing occurrences of
"github-actions" and "github-actions@github.com" with "github-actions[bot]" and
"github-actions[bot]@users.noreply.github.com" respectively (search for the "How
does it work?" heading and the lines describing commit authorship to locate the
text to change).

[sourcery-ai]

New security issues found

[sourcery-ai]

security (python.lang.security.audit.dangerous-subprocess-use-audit): Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'.

Source: opengrep

[sourcery-ai]

security (python.lang.security.audit.dangerous-subprocess-use-audit): Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'.

Source: opengrep

[coderabbitai]

♻️ Duplicate comments (1)

latest_changes/main.py (1)

236-238: ⚠️ Potential issue | 🔴 Critical

git_bin is undefined here, and the hardening migration is incomplete.

Line 236 and Line 238 use git_bin, but no variable is defined in the file, so main() will fail at runtime. Also, remaining git calls still use bare "git" (Lines 247, 259, 261, 264, 269, 270), so the PATH-hardening objective is only partially applied.

Proposed fix

 import logging
 import re
+import shutil
 import subprocess
 import sys
@@
 def main() -> None:
+    git_bin = shutil.which("git")
+    if not git_bin:
+        logging.error("`git` executable not found in PATH")
+        sys.exit(1)
+
@@
-    subprocess.run(["git", "pull"], check=True)
+    subprocess.run([git_bin, "pull"], check=True)
@@
-        subprocess.run(
-            ["git", "add", str(settings.input_latest_changes_file)], check=True
-        )
-        subprocess.run(["git", "commit", "-m", COMMIT_MESSAGE], check=True)
+        subprocess.run([git_bin, "add", str(settings.input_latest_changes_file)], check=True)
+        subprocess.run([git_bin, "commit", "-m", COMMIT_MESSAGE], check=True)
@@
-        result = subprocess.run(["git", "push"])
+        result = subprocess.run([git_bin, "push"])
@@
-        subprocess.run(["git", "reset", "HEAD^1"], check=True)
-        subprocess.run(["git", "checkout", "."], check=True)
+        subprocess.run([git_bin, "reset", "HEAD^1"], check=True)
+        subprocess.run([git_bin, "checkout", "."], check=True)

#!/bin/bash
# Verify `git_bin` is defined and all subprocess git calls use it.
set -euo pipefail

echo "== Check definition of git_bin =="
rg -nP --type=py '\bgit_bin\s*=' latest_changes/main.py || true

echo "== Check subprocess calls still using bare \"git\" =="
rg -nP --type=py 'subprocess\.run\(\[\s*"git"' latest_changes/main.py || true

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@latest_changes/main.py` around lines 236 - 238, The code fails because
git_bin is never defined and some subprocess.run calls still use the literal
"git", so update main() to define git_bin (e.g., resolve the git binary via
shutil.which("git") with a sensible fallback or raise a clear error) before any
subprocess.run usage, then replace every subprocess.run([... "git", ...])
invocation (all occurrences that call subprocess.run with "git" such as the
calls currently at/near the blocks configuring user.name/email and the other git
invocations) to use the git_bin variable instead of the literal "git"; ensure
you import any helper (shutil/os) needed and keep git_bin in scope for all
places that call subprocess.run.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@latest_changes/main.py`:
- Around line 236-238: The code fails because git_bin is never defined and some
subprocess.run calls still use the literal "git", so update main() to define
git_bin (e.g., resolve the git binary via shutil.which("git") with a sensible
fallback or raise a clear error) before any subprocess.run usage, then replace
every subprocess.run([... "git", ...]) invocation (all occurrences that call
subprocess.run with "git" such as the calls currently at/near the blocks
configuring user.name/email and the other git invocations) to use the git_bin
variable instead of the literal "git"; ensure you import any helper (shutil/os)
needed and keep git_bin in scope for all places that call subprocess.run.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3524425a-23d1-48d0-aa5c-52a9577c6624

📥 Commits

Reviewing files that changed from the base of the PR and between ec2822e and 3c3354f.

📒 Files selected for processing (1)

• latest_changes/main.py