update - #10
Conversation
Update DEPLOYMENT_GUIDE.md
Add .well-known/atproto-did with the account DID so Bluesky can verify the domain handle over HTTPS, add .nojekyll so GitHub Pages publishes the dot-folder, and document the setup in the deployment guide.
|
Insufficient balance to process this code review. Please add funds or upgrade your plan in billing. |
There was a problem hiding this comment.
@loganfinney27
Thank you for your contribution to this repository! We appreciate your effort in opening pull request.
Happy coding!
|
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
|
You're down to 6 days left in your trial! Once the trial period is over, new analysis in-editor and PR analyses will pause.Unlock more power with the Standard Plan: View Dashboard |
|
Review these changes at https://app.gitnotebooks.com/LAF-US/loganfinney/pull/10 |
PR Analysis SummaryChange Metrics
Risk factors:
Classification
Files by Type
Analyzed by Woden Tagger • Automated PR insights for better code reviews
💡 Want enhanced Github Projects/Notes and to turn Issues into a Service Desk? Check out Woden Desk on the GitHub Marketplace |
💡 TipWant to run additional checks on this PR?
|
🔍 SEO Review — 3 issues found🔴 Critical (3)
✅ 28 checks passed
SEOCode · Docs & troubleshooting
|
✅ Passed checks (3)
💬 Precogs.ai · Detect. Fix. Merge. |
🤖 CodeAnt AI — Review Status
|
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
🔍 CodeRifts / contract-gateNo OpenAPI schemas found in this repository. Check name is While no schema is found, this check completes neutral, which GitHub treats as non-blocking — so if CodeRifts is a required status check, it is not currently blocking anything on this branch. To get started, either:
schema:
- path/to/your/openapi.yaml📖 Documentation · 💬 Get help ☁️ You're on the Free plan. Pro features (risk scoring, governance, deprecation enforcement) are included during the beta. Lock in Pro pricing → |
There was a problem hiding this comment.
inspect review
Triage: 2 entities analyzed | 0 critical, 0 high, 0 medium, 2 low
Verdict: standard_review
Findings (0)
Reviewed by inspect | Entity-level triage found 0 high-risk changes
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
QWED Security Verification Report3 files scanned | 0 blocked | 0 warnings | 1 info | 0 suppressed | 2 verified Informational Findings
Engines
Verified Files
Verified by QWED — deterministic security verification. No LLM used. Verification Context v1.0{
"spec_version": "1.0",
"object": {
"formal_statement": "LAF-US/loganfinney@7f679e93 (PR #10) is safe to merge"
},
"context": {
"interpretation": {
"theory": "deterministic security verification",
"logic": "evidence-context-policy pipeline"
},
"proof": {
"verifier": "QWED Security",
"verifier_version": "qwed-security-ruleset/1",
"configuration": {
"repo": "LAF-US/loganfinney",
"head_sha": "7f679e9308e7ffe728ebae9c60c6491ac3a6fb49",
"files_scanned": 3
},
"theory_scope": "PR security scan against QWED deterministic rule set",
"trusted_dependencies": [
"qwed-security"
],
"outcome_treatment": "unknown/timeout/error resolve to UNVERIFIABLE or BLOCKED"
},
"evidence": {
"evidence": {
"status": "UNVERIFIABLE",
"agent_message": "PR requires review: 1 advisory finding(s).",
"developer_fields": {
"total_warnings": 1,
"advisory_checks": []
},
"is_authoritative": false,
"scan_evidence": {
"repo": "LAF-US/loganfinney",
"head_sha": "7f679e9308e7ffe728ebae9c60c6491ac3a6fb49",
"pr_number": 10,
"files_scanned": 3,
"engine_results": 5,
"conclusion": "success",
"rule_set": "qwed-security-ruleset/1",
"engines": [
"entropy_scan",
"guard",
"pattern_scan"
]
},
"repo": "LAF-US/loganfinney",
"head_sha": "7f679e9308e7ffe728ebae9c60c6491ac3a6fb49",
"files_scanned": 3
},
"proof_ref": null
},
"decision": {
"admission": "DENY"
}
},
"verdict": "UNVERIFIABLE"
} |
aislop skipped this PRThis workspace does not have an active paid scanaislop plan. Choose a plan to resume hosted scans and PR gates: This comment appears once per PR. Further pushes will be skipped silently until the workspace has paid access. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
There was a problem hiding this comment.
Sorry @loganfinney27, you have reached your weekly rate limit of 250000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
This session could not recover from an error (FatalError: Step "step//eve@0.24.4//turnStep" failed after 3 retries: Sandbox template "eve-sbx-tpl-vercel-b450aeeb2d048167-7971261de91b14688610" is not provisioned for ba…). Start a new comment to continue. Error id: d9b6c4a8-8203-4554-94e1-b01664ab5046 |
Free review limit reachedYou've used your free MergeStorm reviews for this period, so this pull request was not reviewed ( Upgrade for more reviews, or wait until your next period: See plans on the billing page |
There was a problem hiding this comment.
@loganfinney27
Thank you for your contribution to this repository! We appreciate your effort in closing pull request.
Happy coding!
Reviewer's guide (collapsed on small PRs)Reviewer's GuideConfigures Bluesky custom-domain handle verification through a GitHub Pages well-known DID file and documents the files, URL, and deployment constraints needed to preserve verification. Sequence diagram for Bluesky custom-domain handle verificationsequenceDiagram
participant Bluesky
participant GitHubPages
participant Site as loganfinney.com
Bluesky->>Site: GET /.well-known/atproto-did
Site->>GitHubPages: Serve .well-known/atproto-did
GitHubPages-->>Site: Account DID
Site-->>Bluesky: Account DID
Bluesky->>Bluesky: Verify domain handle
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🏆 Insight Code — Accessibility Review
Score
|
| Severity | Checks failed | Occurrences |
|---|---|---|
| 🔴 Critical | 0 | 0 |
| 🟡 Warning | 0 | 0 |
| 🔵 Info | 0 | 0 |
✅ No accessibility issues in this diff
Every check passed on the files you changed. Nice work.
Whole-project findings are filed as issues on push. 🤖 Insight Code · Scan 54995b85-c3bc-4a6a-b458-6ee717e8bd93
Pull Request Summary by devActivityMetricsAchievements
|
|
SummaryCoverage spans the site's core user-facing pages and controls, including navigation, theme behavior, content rotation, and deployment documentation, along with the custom-domain verification flow. It also checks successful responses, exact account identity data, cache consistency, nearby invalid paths, fresh-session behavior, and recovery guidance. Safe to merge — the exercised behaviors are healthy with no regressions or PR-attributable failures, so there is no merge-blocking risk identified. Live provider acceptance remains outside the tested scope and is a flag for later rather than a blocker. Tests run by Ito
Tip Reply with @itoqa to send us feedback on this test run. |
Merge pull request #10 from LAF-US/main

User description
Summary by Sourcery
Enable and document Bluesky domain verification for the GitHub Pages site.
New Features:
Documentation:
CodeAnt-AI Description
Restore Bluesky custom-domain verification for loganfinney.com
What Changed
https://loganfinney.com/.well-known/atproto-didImpact
✅ Bluesky handle verification for @loganfinney.com✅ Reliable custom-domain ownership checks✅ Clearer recovery steps if verification expires💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by cubic
Restores Bluesky custom domain handle verification for
@loganfinney.comusing the HTTPS well-known method. Adds.well-known/atproto-didand.nojekyllso GitHub Pages serves the verification file, and updates DEPLOYMENT_GUIDE.md._atprotoTXT due to a wildcard CNAME..well-known/atproto-didand.nojekyllat the same paths on any new host.Written for commit 7f679e9. Summary will update on new commits.