Skip to content

docs: link the printer series on the blog, not the private site repo - #31

Merged
hallelx2 merged 1 commit into
mainfrom
halleluyaholudele/hal-2846-blog-link
Oct 13, 2026
Merged

hallelx2 merged 1 commit into
mainfrom
halleluyaholudele/hal-2846-blog-link

Conversation

@hallelx2

@hallelx2 hallelx2 commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

docs/README.md linked the Reading a PDF like a printer series to its source in the vectorless repository. That repository went private on 2026-10-13, so the link 404s for anyone signed out. It now points at the published series on blogs.vectorless.store, starting with part 1.

The blog itself had last been deployed 114 days ago, before the series existed, so every post 404'd. I redeployed it from main, and all seven /posts/<slug> pages now return 200.

Closes HAL-2865

Summary by Sourcery

Point the PDF evaluation series documentation to its publicly accessible published articles.

Bug Fixes:

  • Update the documentation link for the seven-part PDF evaluation series to point to its publicly available blog content instead of the private source repository.

Documentation:

  • Link directly to the first published article on the Vectorless blog as the entry point for the series.

Summary by CodeRabbit

  • Documentation
    • Updated the “Reading a PDF like a printer” series link to point to the Vectorless blog’s first post.

The posts' source moved out of public view when the vectorless repo went
private, so the link 404s for anyone signed out. The published series on
blogs.vectorless.store is where readers should land anyway.
@sourcery-ai

sourcery-ai Bot commented Oct 13, 2026 •

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

Reviewer's Guide

The PR fixes the documentation’s broken series link by pointing readers to the public blog and redeploys the blog from main so all seven referenced posts are live.

File-Level Changes

Change Details Files
Update the documentation link from the private source repository to the publicly published blog series.
  • Replace the repository URL with the blog homepage and the first post in the seven-part series.
  • Preserve the explanation that the series describes the evaluation reports.
docs/README.md
Redeploy the blog so the published series is available at its documented URLs.
  • Deploy the blog from main.
  • Verify all seven post routes return HTTP 200.

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 13, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ac213b89-626b-4e74-926b-21eb8ce6bc70
📥 Commits

Reviewing files that changed from the base of the PR and between e187295 and b3e8c16.

📒 Files selected for processing (1)
  • docs/README.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The README publication link now points to the Vectorless blog’s first post, “A PDF is not a document,” instead of the GitHub series directory.

Changes: Documentation link

Layer / File(s) Summary
Update publication link
docs/README.md
The publication link now points to “A PDF is not a document” on the Vectorless blog.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to b3e8c

The README now directs readers to the published PDF series; no merge-blocking issue is evident.

Pre-merge checks · Passed 5
Passed Passed checks (5 passed)
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: updating the printer series link to use the blog instead of the now-private repository.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • 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.

@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 reviewed your changes and they look great!


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

@hallelx2
hallelx2 merged commit 3c6048b into main Oct 13, 2026
2 of 5 checks passed
@hallelx2
hallelx2 deleted the halleluyaholudele/hal-2846-blog-link branch October 13, 2026 08:59
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