Skip to content

docs(repo-health): clone URL, uv run, and CLI bug template - #1258

Merged
abhimehro merged 4 commits into
mainfrom
cursor-agent/repository-health-housekeeping-4aac
Sep 18, 2026
Merged

abhimehro merged 4 commits into
mainfrom
cursor-agent/repository-health-housekeeping-4aac

Conversation

@cursor

@cursor cursor Bot commented Sep 17, 2026

Copy link
Copy Markdown

Submitting a Pull Request

Summary

Weekly housekeeping (2026-09-17): docs and issue template only. Supersedes draft #1248 (still unmerged).

Branch Naming

  • docs/<short-description> (cloud unique prefix cursor-agent/repository-health-housekeeping-4aac)

Before Opening a PR

Docs/template only. uv run pytest --collect-only -q → 590 tests (unchanged).

PR Description

What Changed and Why

Re-land #1248 (still draft on main):

  • Clone URL github.com/your-username/ctrld-sync.git → abhimehro/ctrld-sync.
  • Quick start used bare python main.py; AGENTS.md/CONTRIBUTING already use uv run python.
  • CI table listed only Sync / Bandit / Test; added Lint, Typecheck, and Performance.

New vs last week:

  • WARP.md still told people to edit DEFAULT_FOLDER_URLS in main.py; the list lives in config.py, and config.yaml / --config is the file-based path.
  • Bug report template was the GitHub web-app default (Browser / Smartphone); replaced with CLI/uv fields and a TOKEN/PROFILE redaction note.

Did not bump actions/ai-inference (#1233 / Dependabot #1204). Did not add CODEOWNERS (none of the sibling repos have one).

Include:

  • A summary of what changed and why
  • How to test or verify the change
  • Any relevant issue numbers (e.g., Closes #123)

Security Implications

  • No secrets or credentials are introduced or exposed by this change

Secrets

TOKEN (Control D API token) and PROFILE (profile ID) are required only for live runs against the API. Not used by this PR.

Checklist

  • Commit messages are clear and descriptive
  • Documentation updated if behaviour changed (README, docstrings, etc.)
  • No secrets, credentials, tokens, profiles, or .env files are included in this PR

Please keep this draft until reviewed.

═══ ELIR ═══
PURPOSE: Mechanical docs/template hygiene so clone/run/CI and bug reports match the Python 3.13 + uv CLI.
SECURITY: No secrets, no workflow pin changes, no ai-inference bump.
FAILS IF: someone still follows the old #1248 branch instead of this one.
VERIFY: README clone URL is abhimehro/ctrld-sync; WARP.md names config.py; bug template has no Browser/Smartphone.
MAINTAIN: Close or supersede leftover draft #1248 after merge; hold Models 410 on summary.yml.

Open in Web View Automation 

cursoragent and others added 2 commits September 17, 2026 12:09
Re-lands the unmerged 2026-09-10 housekeeping (#1248): clone
abhimehro/ctrld-sync, match AGENTS.md uv run commands, and list
lint/typecheck/performance beside test/sync/bandit.

Co-authored-by: abhimehrotra <abhimehrotra@bears.mybrcc.edu>
DEFAULT_FOLDER_URLS lives in config.py, not main.py; document
config.yaml/--config as the file-based path. Replace the
web-app bug report template with CLI/uv environment fields.

Co-authored-by: abhimehrotra <abhimehrotra@bears.mybrcc.edu>
@trunk-io

trunk-io Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

😎 This pull request was merged.

@coderabbitai

coderabbitai Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 5cef4a8a-69a1-456d-b657-7c48216c9c61

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
✨ Simplify code
  • Commit to this branch
  • Create a new PR

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

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

@github-actions

github-actions Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

Visual recap — skipped

The visual recap job did not run for this pull request. This is informational only and does not block the PR.

Recap skipped for 664f2cf: bot author (type=Bot).

@github-actions

github-actions Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 369130d.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

@github-actions github-actions Bot added documentation Improvements or additions to documentation configuration labels Sep 17, 2026
@abhimehro

abhimehro commented Sep 17, 2026 •

Copy link
Copy Markdown
Owner

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

codescene-access[bot]

This comment was marked as outdated.

@codacy-production

codacy-production Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

Not up to standards ⛔

🔴 Issues 6 minor

Alerts:
⚠ 6 issues (≤ 0 issues of at least minor severity)

Results:
6 new issues

Category Results
CodeStyle 6 minor

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@cursor
cursor Bot requested a review from abhimehro September 17, 2026 12:19
@abhimehro abhimehro self-assigned this Sep 18, 2026
@abhimehro
abhimehro marked this pull request as ready for review September 18, 2026 02:10
Copilot AI lite review requested due to automatic review settings September 18, 2026 02:10

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Align repository guidance and bug reports with the uv CLI

📝 Documentation ✨ Enhancement 🕐 10-20 Minutes

Grey Divider

AI Description

• Correct clone and uv-based run instructions for the supported setup.
• Document all CI checks and accurate folder configuration sources.
• Tailor bug reports to CLI diagnostics and credential-safe reproduction details.
Diagram

graph TD
  Contributor["Contributor"] --> Readme["README Quick Start"] --> CLI["uv CLI"]
  Contributor --> Warp["WARP Guidance"] --> Config["Config Sources"]
  Reporter["Bug Reporter"] --> Template["CLI Bug Template"] --> Issue["Actionable Report"]
Loading
High-Level Assessment

Directly correcting the existing README, WARP guide, and Markdown issue template is the lowest-risk approach. A migration to GitHub issue forms could enforce structured fields, but it would add configuration scope without improving the documentation corrections targeted by this PR.

Files changed (3) +35 / -34

Enhancement (1) +18 / -21
bug_report.mdReplace web-oriented prompts with CLI diagnostics +18/-21

Replace web-oriented prompts with CLI diagnostics

• Reworks the bug report template around exact uv commands, clean-clone reproduction steps, runtime versions, and observed output. Adds explicit instructions to redact Control D tokens and profile IDs.

.github/ISSUE_TEMPLATE/bug_report.md

Bug fix (1) +3 / -2
WARP.mdCorrect blocklist configuration guidance +3/-2

Correct blocklist configuration guidance

• Points built-in folder URL customization to config.py instead of main.py. Documents config.yaml and the --config option as the file-based configuration path.

WARP.md

Documentation (1) +14 / -11
README.mdCorrect setup commands and complete the CI workflow table +14/-11

Correct setup commands and complete the CI workflow table

• Updates the clone URL to the canonical repository and runs all documented commands through uv. Expands the CI table to include lint, type-checking, and performance workflows.

README.md

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates documentation and issue templates to align with the uv toolchain and current project standards. However, the analysis indicates that the PR is currently not up to standards, primarily due to multiple formatting violations in the README.

While the transition to uv run is correctly applied in most areas, it has introduced line-length issues (MD013) in the command examples. Additionally, the CI/CD workflow table requires more consistent terminology to match the rest of the documentation. Please verify that the bug report template and repository clone URL updates have been fully implemented as per the acceptance criteria.

About this PR

  • The documentation updates introduce several style violations, specifically line length exceeds in the README. These must be addressed to maintain the project's quality standards.

Test suggestions

  • Verify that all documented bash examples for running the script utilize the 'uv run' prefix
  • Validate that the Bug report template correctly prompts for CLI environment details (OS, Python, uv, version/commit)
  • Confirm the clone URL in the 'Clone & install' section matches the target repository 'abhimehro/ctrld-sync'
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that all documented bash examples for running the script utilize the 'uv run' prefix
2. Validate that the Bug report template correctly prompts for CLI environment details (OS, Python, uv, version/commit)
3. Confirm the clone URL in the 'Clone & install' section matches the target repository 'abhimehro/ctrld-sync'

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread README.md
Comment on lines +139 to +141
uv run python main.py --dry-run # plan only, no API calls
uv run python main.py --dry-run --plan-json plan.json # machine-readable dry-run output
uv run python main.py --profiles your_id # live run (requires TOKEN)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ LOW RISK

Suggestion: Reduce the excessive padding between the command and its descriptive comment to fit within the 80-character limit.

This might be a simple fix:

Suggested change
uv run python main.py --dry-run # plan only, no API calls
uv run python main.py --dry-run --plan-json plan.json # machine-readable dry-run output
uv run python main.py --profiles your_id # live run (requires TOKEN)
uv run python main.py --dry-run # plan only, no API calls
uv run python main.py --dry-run --plan-json plan.json # JSON plan output
uv run python main.py --profiles your_id # live run (requires TOKEN)

Comment thread README.md
| **Test** | `test.yml` | Push/PR to `main` | Full pytest suite via `uv sync --all-extras` |
| Workflow | File | Trigger | Purpose |
| --------------- | ----------------- | ----------------------------------- | -------------------------------------------------------------------------------- |
| **Sync** | `sync.yml` | Daily at 02:00 UTC, manual dispatch | Main synchronization workflow — runs `main.py` to keep Control D folders in sync |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ LOW RISK

Nitpick: To maintain consistency with the rest of the documentation and the 'Test' workflow description below, consider mentioning uv here.

Suggested change
| **Sync** | `sync.yml` | Daily at 02:00 UTC, manual dispatch | Main synchronization workflow — runs `main.py` to keep Control D folders in sync |
**Sync** | `sync.yml` | Daily at 02:00 UTC, manual dispatch | Main synchronization workflow — runs `main.py` via `uv` to keep Control D folders in sync |

@qodo-code-review

qodo-code-review Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Action required

No findings for this group


Remediation recommended

1. The workflow table overstates checks ✓ Resolved 🟠 Medium 🐞 Bug ≡ Correctness
Description
The new Performance row says performance.yml runs for every pull request to main, but that
workflow applies pull-request path filters. Pull requests that do not modify the four configured
code, benchmark, or workflow paths—such as this documentation-only PR—do not receive that check.
Code

README.md[306]

+| **Performance** | `performance.yml` | Push/PR to `main`                   | Performance regression checks                                                    |
Relevance

●●● Strong

Recent PRs accepted corrections to inaccurate README workflow descriptions and CI trigger
documentation.

PR-#1162
PR-#392
PR-#398

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The added README row advertises an unrestricted pull-request trigger, while the workflow's
pull_request.paths block restricts execution to changes in main.py, benchmark data, the workflow
itself, and designated performance tests.

README.md[306-306]
.github/workflows/performance.yml[3-10]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The CI workflow table says performance checks run for all pull requests to `main`, while the workflow limits pull-request execution to selected paths.

## Fix Focus Areas
- README.md[306-306]
- .github/workflows/performance.yml[3-10]

## Recommended Fix
Change the Performance trigger description to state that pushes to `main` run it, while pull requests run it only for performance-related paths.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Informational

No findings for this group

Grey Divider

Context sources
✅ Compliance rules (platform): 11 rules
✅ Cross-repo context — repo relationships
✅ REVIEW.md

Grey Divider

Tip of the day
💡 Did you know, you can type 'qodo, fix this' on a finding and the fix lands right on your PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread README.md Outdated
@qodo-code-review

Copy link
Copy Markdown

Qodo Fixer

✅ Committed (1) · ☑ Fixed (1)

Grey Divider

Commits pushed directly to this PR — no separate fix PR opened.

Process — 1 fixed
  • ☑ Fixed: The workflow table overstates checks

codescene-access[bot]

This comment was marked as outdated.

@snyk-io

snyk-io Bot commented Sep 18, 2026

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@codescene-access codescene-access Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No application code in the PR — skipped Code Health checks.

See analysis details in CodeScene

Quality Gate Profile: Clean Code Collective
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.

@abhimehro
abhimehro merged commit cf47067 into main Sep 18, 2026
17 of 19 checks passed
@abhimehro
abhimehro deleted the cursor-agent/repository-health-housekeeping-4aac branch September 18, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants