Skip to content

update - #10

Merged
loganfinney27 merged 2 commits into
loganfrom
main
Aug 24, 2026
Merged

update#10
loganfinney27 merged 2 commits into
loganfrom
main

Conversation

@loganfinney27

@loganfinney27 loganfinney27 commented Aug 24, 2026

Copy link
Copy Markdown
Member

User description

Summary by Sourcery

Enable and document Bluesky domain verification for the GitHub Pages site.

New Features:

  • Add Bluesky custom-domain handle verification using the HTTPS well-known file method.

Documentation:

  • Document the files and re-verification steps required to preserve Bluesky handle verification on GitHub Pages.

CodeAnt-AI Description

Restore Bluesky custom-domain verification for loganfinney.com

What Changed

  • Adds the verification file Bluesky fetches at https://loganfinney.com/.well-known/atproto-did
  • Keeps GitHub Pages from excluding the hidden verification path
  • Documents the verification setup, recovery steps, and hosting requirements

Impact

✅ 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:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

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:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

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.com using the HTTPS well-known method. Adds .well-known/atproto-did and .nojekyll so GitHub Pages serves the verification file, and updates DEPLOYMENT_GUIDE.md.

  • Review: Confirm https://loganfinney.com/.well-known/atproto-did returns did:plc:o2tkkq3qnpzfbsozy3nqkssu.
  • Rollout: No DNS changes; we avoid _atproto TXT due to a wildcard CNAME.
  • Migration: Preserve .well-known/atproto-did and .nojekyll at the same paths on any new host.

Written for commit 7f679e9. Summary will update on new commits.

Review in cubic

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.
@semanticdiff-com

Copy link
Copy Markdown

Review changes with  SemanticDiff

@tenki-reviewer

Copy link
Copy Markdown

Insufficient balance to process this code review. Please add funds or upgrade your plan in billing.

@gitginie gitginie 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.

@loganfinney27
Thank you for your contribution to this repository! We appreciate your effort in opening pull request.
Happy coding!

@cr-gpt

cr-gpt Bot commented Aug 24, 2026

Copy link
Copy Markdown

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

@codesherlock-ai

Copy link
Copy Markdown

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

@gitnotebooks

gitnotebooks Bot commented Aug 24, 2026

Copy link
Copy Markdown

Review these changes at https://app.gitnotebooks.com/LAF-US/loganfinney/pull/10

@pr-insights-tagger

Copy link
Copy Markdown

PR Analysis Summary

Risk Level Complexity Files Changed

📧 Email-friendly summary
Risk: 🟢 Low Risk | Complexity: 🟢 0.44/10 | Files: 3

Change Metrics

Metric Value
Lines Added +14
Lines Deleted -0
Files Modified 3
Complexity Score 🟢 0.44/10
Risk Assessment 🟢 Low Risk

Risk factors:

  • Low complexity score (0.4/10)

Classification

size:small type:maintenance docs:markdown

Files by Type

nojekyll ▰▰▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱ 1 file
well-known/atproto-did ▰▰▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱ 1 file
md ▰▰▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱▱ 1 file


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

@codesherlock-ai

Copy link
Copy Markdown

💡 Tip

Want to run additional checks on this PR?

  • Comment @codesherlock-ai analyze owasp to trigger an OWASP Top-10 security analysis.
  • Comment @codesherlock-ai analyze cwe_mitre to trigger a CWE-MITRE mapping analysis.
  • Comment @codesherlock-ai analyze cwe_kev to trigger a CWE-KEV (Known Exploited Vulnerabilities) analysis.

@seoguard

seoguard Bot commented Aug 24, 2026

Copy link
Copy Markdown

🔍 SEO Review — 3 issues found

🔴 Critical (3)

File Issue Fix
index.html Missing meta description
Meta descriptions are used as SERP snippets. Without one, Google auto-generates one from page content, which is typical…
Add <meta name="description" content="Your description here (150-160 chars)" /> inside <head>
resume.html Missing meta description
Meta descriptions are used as SERP snippets. Without one, Google auto-generates one from page content, which is typical…
Add <meta name="description" content="Your description here (150-160 chars)" /> inside <head>
work.html Missing meta description
Meta descriptions are used as SERP snippets. Without one, Google auto-generates one from page content, which is typical…
Add <meta name="description" content="Your description here (150-160 chars)" /> inside <head>
✅ 28 checks passed
  • image-missing-alt
  • missing-title
  • missing-h1
  • multiple-h1
  • image-missing-alt
  • missing-lang
  • missing-viewport
  • accidental-noindex
  • invalid-json-ld
  • back-button-hijacking
  • missing-title
  • missing-h1
  • multiple-h1
  • image-missing-alt
  • missing-lang
  • missing-viewport
  • accidental-noindex
  • invalid-json-ld
  • back-button-hijacking
  • missing-title
  • missing-h1
  • multiple-h1
  • image-missing-alt
  • missing-lang
  • missing-viewport
  • accidental-noindex
  • invalid-json-ld
  • back-button-hijacking

SEOCode Free — you're seeing 10 core rules. 44 more issues on this PR would be caught with Pro — performance, structured data, internationalisation and more. Upgrade to Pro ($29/mo).


SEOCode · Docs & troubleshooting

⚠️ This repository is beyond the Free plan's 1-repository limit. It's still being reviewed for now, but reviews here will require a paid plan after 2026-09-15. See plans.

@precogs-ai

precogs-ai Bot commented Aug 24, 2026

Copy link
Copy Markdown

✅ Precogs scan complete — No security issues found

Commit 7f679e9 on main · 3 files scanned

🔴 Critical 🟠 High 🔵 Medium 🟢 Low 🎯 Risk Score
0 0 0 0 0.0

All clear. We scanned for SQL injection, XSS, hardcoded secrets, vulnerable dependencies, IaC misconfigurations, and PII exposure. No security vulnerabilities were detected in this PR.

Passed checks (3)
Check Status Details
Code scan (SAST) ✅ Passed No vulnerabilities detected
Secrets scan ✅ Passed No hardcoded credentials found
Dependency audit ✅ Passed No known CVEs

💬 @precogs-ai help for commands · 🔗 View report

Precogs.ai · Detect. Fix. Merge.

@codeant-ai

codeant-ai Bot commented Aug 24, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 7f679e9 Aug 24, 2026 · 19:32 19:33

@codereviewbot-ai

Copy link
Copy Markdown

🤖 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

coderifts Bot commented Aug 24, 2026

Copy link
Copy Markdown

🔍 CodeRifts / contract-gate

No OpenAPI schemas found in this repository.

Check name is CodeRifts / contract-gate (was CodeRifts — API Contract Check). Required-check setups pinned to the old name keep passing until you re-pin.

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:

  • Name your OpenAPI schema file openapi.yaml (or openapi.json, swagger.yaml, etc.)
  • Or add a .coderifts.yml to specify the path:
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 →

@inspect-review inspect-review 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.

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-code-review

Copy link
Copy Markdown

ⓘ 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

qwed-security Bot commented Aug 24, 2026

Copy link
Copy Markdown

QWED Security Verification Report

3 files scanned | 0 blocked | 0 warnings | 1 info | 0 suppressed | 2 verified

Informational Findings

File Line Context Issue
.nojekyll L1 UNKNOWN Empty file contains no scannable content.

Engines

  • entropy_scan: ✅
  • guard: ⚠️ 1 finding(s)
  • pattern_scan: ✅

Verified Files

  • .well-known/atproto-did
  • DEPLOYMENT_GUIDE.md

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"
}

@scan-ai-slop-aislop

Copy link
Copy Markdown

aislop skipped this PR

This workspace does not have an active paid scanaislop plan. Choose a plan to resume hosted scans and PR gates:

Choose a paid plan

This comment appears once per PR. Further pushes will be skipped silently until the workspace has paid access.

@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 231388fc-8409-47d5-88ab-6c646bcc80e3

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

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.

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

Sorry @loganfinney27, you have reached your weekly rate limit of 250000 diff characters.

Please try again later or upgrade to continue using Sourcery

@testdriverai

testdriverai Bot commented Aug 24, 2026

Copy link
Copy Markdown

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

@loganfinney27
loganfinney27 merged commit 40d6167 into logan Aug 24, 2026
22 of 29 checks passed
@mergestorm-vortex

Copy link
Copy Markdown

Free review limit reached

You've used your free MergeStorm reviews for this period, so this pull request was not reviewed (7f679e9).

Upgrade for more reviews, or wait until your next period: See plans on the billing page

@gitginie gitginie 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.

@loganfinney27
Thank you for your contribution to this repository! We appreciate your effort in closing pull request.
Happy coding!

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Aug 24, 2026
@sourcery-ai

sourcery-ai Bot commented Aug 24, 2026

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

Reviewer's Guide

Configures 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 verification

sequenceDiagram
    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
Loading

File-Level Changes

Change Details Files
Add Bluesky HTTPS well-known domain verification support and document its hosting requirements.
  • Add .well-known/atproto-did containing the Bluesky account DID.
  • Document the verification URL, required .nojekyll behavior, re-verification steps, and DNS verification rationale.
.well-known/atproto-did
DEPLOYMENT_GUIDE.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

@insight-code-accessibility

insight-code-accessibility Bot commented Aug 24, 2026

Copy link
Copy Markdown

🏆 Insight Code — Accessibility Review

Reviewing the 3 file(s) this pull request changes.

Score ████████████████████ 100/100 · Grade A

47 of 47 checks passed. A check counts once, however many times it is hit.

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

@devactivity-app

Copy link
Copy Markdown

Pull Request Summary by devActivity

Metrics

Cycle Time: 25m Review Time: < 1 min Comments: 11

Achievements

@itoqa

itoqa Bot commented Aug 24, 2026

Copy link
Copy Markdown

Ito QA test results
Commit: 7f679e9: 6 test cases ran, 6 passed ✅.

Summary

Coverage 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

View full run

Result Severity Type Description
General The exact verification route stayed on the local site and returned the expected DID. A nearby path returned its own 404 page, and a fresh browser context downloaded the same file without leaving the site.
General The verification file returned the same exact DID for the baseline and cache-busted requests. Fresh local checks stayed successful and did not return stale or extra content.
Rev The local verification URL returned HTTP 200 and exactly the expected account DID. The live Bluesky account flow was not opened because this run allows local checks only, so provider acceptance remains untested.
Rev The home, Work, and Resume pages loaded correctly. The theme stayed dark after reload, the hero image changed, and the browser reported no errors.
Rev The guide names the right files, domain, verification path, DID, and recovery steps. The local verification file returned the expected DID.
Verify The verification URL returned the expected DID with a successful response and no extra content. Bluesky can read the account DID from this file.

Tip

Reply with @itoqa to send us feedback on this test run.

loganfinney27 added a commit that referenced this pull request Aug 24, 2026
Merge pull request #10 from LAF-US/main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs:markdown size/S size:S This PR changes 10-29 lines, ignoring generated files 🏷️ type:maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant