-
Notifications
You must be signed in to change notification settings - Fork 0
Anchor audit agent paths to project root #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anchor audit agent paths to project root #19
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…t root Co-authored-by: groupthinking <154503486+groupthinking@users.noreply.github.com>
f2a91b8
into
jules-audit-agent-16337681246389421261
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request fixes a path resolution issue in the nightly audit agent script that caused failures when executed from cron or outside the repository root directory. The change anchors the log_dir and report_dir paths to the project root using Path(__file__).resolve().parent.parent, ensuring consistent path resolution regardless of the working directory from which the script is invoked.
Changes:
- Anchored
log_dirandreport_dirpaths to project root inscripts/nightly_audit_agent.py
Comments suppressed due to low confidence (2)
scripts/nightly_audit_agent.py:17
- Import of 'os' is not used.
import os
scripts/nightly_audit_agent.py:22
- Import of 'List' is not used.
Import of 'Optional' is not used.
from typing import Dict, List, Any, Optional
The nightly audit agent used relative paths for
log_dirandreport_dir, causing failures when executed from cron or outside the repository root.Changes:
log_dirandreport_dirto project root usingPath(__file__).resolve().parent.parentscripts/scheduled_cleanup.py:221Before:
After:
This ensures paths resolve consistently regardless of execution context (cron, manual invocation, different working directories).
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.