Repository navigation
chore: update repository references to veriframe and resolve B9 #21
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -95,7 +95,7 @@ VeriFrame is a video deepfake screening platform and reviewer console built on t | |
|
|
||
| ```bash | ||
| # Clone and enter repository | ||
| git clone https://github.com/ADITYASINGH1206/sentinel-v.git | ||
| git clone https://github.com/ADITYASINGH1206/veriframe.git | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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, Change the clone command to clone Prompt for AI agentsIn `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. |
||
| cd sentinel-v | ||
|
|
||
| # Initialize development environment | ||
|
|
@@ -150,7 +150,7 @@ VeriFrame is built concurrently across two parallel workstreams: | |
| - SENTINEL platform integration adapter (M8) | ||
| - Security hardening, SSRF sandboxing, and load testing (M11) | ||
|
|
||
| See [GitHub Issues](https://github.com/ADITYASINGH1206/sentinel-v/issues) for detailed task specifications and acceptance criteria. | ||
| See [GitHub Issues](https://github.com/ADITYASINGH1206/veriframe/issues) for detailed task specifications and acceptance criteria. | ||
|
|
||
| --- | ||
|
|
||
|
|
||
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.
🔍 Update Clone Command to New Repository Name
The
cd sentinel-vcommand should also be updated to reflect the new repository name for consistency and to avoid confusion if the user clones intoveriframe.