Skip to content

chore: update repository references to veriframe and resolve B9 - #21

Merged
ADITYASINGH1206 merged 1 commit into
mainfrom
chore/rename-repo-references
Oct 29, 2026
Merged

ADITYASINGH1206 merged 1 commit into
mainfrom
chore/rename-repo-references

Conversation

@ADITYASINGH1206

@ADITYASINGH1206 ADITYASINGH1206 commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

Updates all README, brand, and bot configuration references to point to the renamed repository https://github.com/ADITYASINGH1206/veriframe, resolving Blocker B9.

Summary by Sourcery

Update repository references to the renamed VeriFrame GitHub repository and resolve blocker B9.

Bug Fixes:

  • Update repository links and defaults across documentation, branding, and the Gemini PR reviewer to use the renamed VeriFrame repository.

Enhancements:

  • Mark blocker B9 as resolved after completing the repository rename and URL updates.

Documentation:

  • Update README and Gemini PR bot setup documentation with the current repository URL.

@ADITYASINGH1206
ADITYASINGH1206 merged commit b1db4d4 into main Oct 29, 2026
@sourcery-ai

sourcery-ai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR completes the repository rename migration by replacing sentinel-v references with ADITYASINGH1206/veriframe in user documentation, the canonical web brand URL, Gemini PR bot fallback configuration, and blocker tracking.

File-Level Changes

Change Details Files
Updated repository references across documentation, branding, and automation to use the renamed veriframe repository.
  • Changed clone and Issues URLs in the main README.
  • Updated the Gemini PR bot setup link and its fallback GitHub repository.
  • Changed the web brand configuration’s canonical repository URL.
README.md
docs/GEMINI_PR_BOT_SETUP.md
scripts/gemini_pr_reviewer.py
web/src/brand.ts
Marked the repository rename blocker as resolved with the completed rename and URL updates documented.
  • Updated B9 acceptance status and recorded the new repository location.
docs/QUESTIONS.md

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

@coderabbitai

coderabbitai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

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
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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 Oct 29, 2026 •

Copy link
Copy Markdown

🤖 SENTINEL-V DeepForensics AI Review

Status Target PR Author Review Engine
✅ APPROVE #21 - chore: update repository references to veriframe and resolve B9 @ADITYASINGH1206 Google Gemini DeepForensics

📋 1. Executive Summary

This pull request successfully executes task B9 from the project tracking documentation by updating all repository references, documentation links, clone URLs, and default script fallbacks from sentinel-v to the renamed repository veriframe. The changes ensure that brand identity (web/src/brand.ts), local developer setup instructions, and GitHub PR bot configurations remain consistent with the new repository name. All modifications are purely organizational and metadata-focused, maintaining full compliance with the project's security and architecture rules.


🛡️ 2. Specification & Policy Compliance Checklist

Rule / Invariant Status Details / Audit Finding
No Hardcoded / Invented Results ✅ Pass No metrics, benchmarks, or calibration coefficients are introduced or modified in this PR.
Locked Core Untouched (Additive Only) ✅ Pass Core SENTINEL platform files and base deepfake code are untouched; changes are purely cosmetic documentation and config updates.
Upstream Submodule Purity (smsdt) ✅ Pass The third_party/smsdt submodule remains completely unperturbed.
Forbidden Copy Compliance ✅ Pass No UI strings or API responses were altered; forbidden terms are absent from the diff.
Unit & Integration Test Coverage ✅ Pass This PR consists entirely of configuration and documentation updates requiring no logic or test modifications.
Security, Secrets & Sandboxing ✅ Pass No credentials, API tokens, or insecure shell subroutines were added or exposed.

🔍 3. Deep Forensic Findings & Vulnerability Analysis

🔴 [BLOCKING] Issues (Must resolve before merge)

None detected.

🟡 [WARNING] Architectural & Code Quality Improvements

  • Potential clone instruction mismatch in README.md: While the repository URL was updated to veriframe.git, line 98 shows cd sentinel-v.
    git clone https://github.com/ADITYASINGH1206/veriframe.git
    cd sentinel-v
    Since the repository was renamed to veriframe, the resulting local directory created by git clone will typically be veriframe unless explicitly overridden. This could cause a minor friction point for new developers following the quickstart guide.

🟢 [VERIFIED] Strengths & Positive Highlights

  • Comprehensive Refactoring: The author systematically updated all occurrences of the old repository name across documentation (QUESTIONS.md, GEMINI_PR_BOT_SETUP.md, README.md), automation scripts (scripts/gemini_pr_reviewer.py), and frontend branding (web/src/brand.ts).
  • Accurate Status Tracking: Task B9 in docs/QUESTIONS.md was correctly transitioned from OPEN to RESOLVED with appropriate context notes.

💡 4. Actionable Next Steps

  1. Fix Clone Directory Reference: Update the cd sentinel-v command in README.md to cd veriframe to match the new repository name.
  2. Merge PR: Proceed with merging after minor documentation adjustment.

⚠️ Mandatory Screening Aid Notice: Screening aid — not proof. Human review required for consequential action.


5. Inline Actionable Suggestions (FOR CONVERSATIONS)

Comment thread README.md
```bash
# Clone and enter repository
git clone https://github.com/ADITYASINGH1206/sentinel-v.git
git clone https://github.com/ADITYASINGH1206/veriframe.git

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Update Clone Command to New Repository Name

The cd sentinel-v command should also be updated to reflect the new repository name for consistency and to avoid confusion if the user clones into veriframe.

Suggested change
git clone https://github.com/ADITYASINGH1206/veriframe.git
cd veriframe

@sourcery-ai sourcery-ai 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.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="README.md" line_range="98" />
<code_context>
 ```bash
 # Clone and enter repository
-git clone https://github.com/ADITYASINGH1206/sentinel-v.git
+git clone https://github.com/ADITYASINGH1206/veriframe.git
 cd sentinel-v

</code_context>
<issue_to_address>
**Development setup stops after clone**

When a user follows the README clone instructions from a fresh directory, `git clone` creates a `veriframe/` directory, so `cd sentinel-v` fails with “No such file or directory” and the documented setup stops.

Change the clone command to clone `sentinel-v.git` so its directory matches the following `cd sentinel-v` command.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: README.md:98


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

Comment thread README.md
```bash
# Clone and enter repository
git clone https://github.com/ADITYASINGH1206/sentinel-v.git
git clone https://github.com/ADITYASINGH1206/veriframe.git

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟠 High · Development setup stops after clone

When a user follows the README clone instructions from a fresh directory, git clone creates a veriframe/ directory, so cd sentinel-v fails with “No such file or directory” and the documented setup stops.

Change the clone command to clone sentinel-v.git so its directory matches the following cd sentinel-v command.

Prompt for AI agents
In `README.md` at line 98:

**Development setup stops after clone**

When a user follows the README clone instructions from a fresh directory, `git clone` creates a `veriframe/` directory, so `cd sentinel-v` fails with “No such file or directory” and the documented setup stops.

Change the clone command to clone `sentinel-v.git` so its directory matches the following `cd sentinel-v` command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant