Skip to content

Conversation

@pharmacist-sabot
Copy link
Owner

@pharmacist-sabot pharmacist-sabot commented Dec 31, 2025

Summary by Sourcery

Enhancements:

  • Replace generic placeholder hero images with dedicated cover images for multiple blog articles to better match their content.

Summary by CodeRabbit

  • Style
    • Enhanced blog post cover images with custom artwork across multiple articles for improved visual presentation and consistency throughout the blog.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link

vercel bot commented Dec 31, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
rxdevnotes Ready Ready Preview, Comment Dec 31, 2025 6:26am

@sourcery-ai
Copy link

sourcery-ai bot commented Dec 31, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates multiple blog posts to use dedicated, content-specific hero images instead of shared placeholder assets by changing the heroImage paths in their frontmatter.

File-Level Changes

Change Details Files
Switch blog posts from generic placeholder hero images to specific per-article hero assets.
  • Update heroImage path in React roadmap (part 1) post frontmatter to its new blog-specific image
  • Update heroImage path in Vue roadmap (part 2) post frontmatter to its new blog-specific image
  • Update heroImage path in Git commit messages post frontmatter to its new blog-specific image
  • Update heroImage path in Google Apps Script drug search app post frontmatter to its new blog-specific image
  • Update heroImage path in Google Apps Script intro post frontmatter to its new blog-specific image
  • Update heroImage path in Haskell EP.1 post frontmatter to its new blog-specific image
  • Update heroImage path in Haskell EP.2 post frontmatter to its new blog-specific image
  • Update heroImage path in Python learning guide post frontmatter to its new blog-specific image
  • Update heroImage path in Web Accessibility 101 post frontmatter to its new blog-specific image
src/content/blog/frontend-developer-roadmap-part-1/index.mdx
src/content/blog/frontend-developer-roadmap-part-2/index.mdx
src/content/blog/git-commit-messages/index.mdx
src/content/blog/google-app-script-drug-search-app/index.mdx
src/content/blog/google-app-script/index.mdx
src/content/blog/haskell-ep1/index.mdx
src/content/blog/haskell-ep2/index.mdx
src/content/blog/learn-python-with-ritesh-chauhan/index.mdx
src/content/blog/web-accessibility-101/index.mdx

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
Copy link

coderabbitai bot commented Dec 31, 2025

📝 Walkthrough

Walkthrough

This PR updates the heroImage front matter field across nine blog posts, replacing generic placeholder image paths with specific cover images for each article.

Changes

Cohort / File(s) Summary
Blog post cover image updates
src/content/blog/frontend-developer-roadmap-part-1/index.mdx, src/content/blog/frontend-developer-roadmap-part-2/index.mdx, src/content/blog/git-commit-messages/index.mdx, src/content/blog/google-app-script-drug-search-app/index.mdx, src/content/blog/google-app-script/index.mdx, src/content/blog/haskell-ep1/index.mdx, src/content/blog/haskell-ep2/index.mdx, src/content/blog/learn-python-with-ritesh-chauhan/index.mdx, src/content/blog/web-accessibility-101/index.mdx
Updated heroImage paths from generic placeholders (e.g., /images/common/blog-placeholder-X.png) to specific cover images under /images/blog/{post-name}/ directory. No content, logic, or other metadata changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Poem

🐰 Cover images bloom where placeholders stood,
Nine blog posts dressed in their finest good,
From generic to splendid, each post now shines,
With specific covers and beautiful designs!

Pre-merge checks

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'refactor: remove and rename images to blog content' accurately summarizes the main change: updating heroImage paths across 9 blog posts from generic placeholders to specific content-related cover images.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c0f56a5 and a2257b2.

⛔ Files ignored due to path filters (9)
  • public/images/blog/frontend-developer-roadmap-part-1/frontend-roadmap-part-1-cover.png is excluded by !**/*.png
  • public/images/blog/frontend-developer-roadmap-part-2/frontend-roadmap-part-2-cover.png is excluded by !**/*.png
  • public/images/blog/git-commit-messages/git-commit-messages-cover.png is excluded by !**/*.png
  • public/images/blog/google-app-script-drug-search-app/google-app-script-drug-search-cover.png is excluded by !**/*.png
  • public/images/blog/google-app-script/google-app-script-cover.png is excluded by !**/*.png
  • public/images/blog/haskell-ep1/haskell-ep1-cover.png is excluded by !**/*.png
  • public/images/blog/haskell-ep2/haskell-ep2-cover.png is excluded by !**/*.png
  • public/images/blog/learn-python-with-ritesh-chauhan/python-course-cover.png is excluded by !**/*.png
  • public/images/blog/web-accessibility-101/web-accessibility-101-cover.png is excluded by !**/*.png
📒 Files selected for processing (9)
  • src/content/blog/frontend-developer-roadmap-part-1/index.mdx
  • src/content/blog/frontend-developer-roadmap-part-2/index.mdx
  • src/content/blog/git-commit-messages/index.mdx
  • src/content/blog/google-app-script-drug-search-app/index.mdx
  • src/content/blog/google-app-script/index.mdx
  • src/content/blog/haskell-ep1/index.mdx
  • src/content/blog/haskell-ep2/index.mdx
  • src/content/blog/learn-python-with-ritesh-chauhan/index.mdx
  • src/content/blog/web-accessibility-101/index.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Sourcery review
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (9)
src/content/blog/google-app-script/index.mdx (1)

5-5: LGTM!

The heroImage path update is consistent with the PR's pattern for content-specific cover images.

src/content/blog/learn-python-with-ritesh-chauhan/index.mdx (1)

5-5: LGTM!

The heroImage path update works correctly. Note that the filename (python-course-cover.png) uses a slightly different convention compared to other files which use the slug name directly (e.g., haskell-ep1-cover.png). This is a minor inconsistency but not a functional issue.

src/content/blog/frontend-developer-roadmap-part-1/index.mdx (1)

5-5: LGTM!

The heroImage path update follows the established pattern with an appropriately abbreviated filename for this longer slug.

src/content/blog/haskell-ep2/index.mdx (1)

5-5: LGTM!

The heroImage path update is consistent with the PR's pattern for content-specific cover images.

src/content/blog/web-accessibility-101/index.mdx (1)

5-5: LGTM!

The heroImage path update follows the established naming convention.

src/content/blog/git-commit-messages/index.mdx (1)

5-5: LGTM!

The heroImage path update follows the established naming convention.

src/content/blog/haskell-ep1/index.mdx (1)

5-5: LGTM!

The heroImage file exists at the specified path. However, the blog post image naming is not strictly consistent—while some posts use a -cover.png suffix (like frontend-roadmap-part-1-cover.png), others use -hero.png or completely different names. The change itself is correct and valid.

src/content/blog/google-app-script-drug-search-app/index.mdx (1)

5-5: LGTM!

The heroImage path update follows the established pattern for content-specific cover images. All referenced hero images exist in the repository.

src/content/blog/frontend-developer-roadmap-part-2/index.mdx (1)

5-5: Good organizational improvement.

The change from a generic placeholder to a post-specific cover image improves maintainability and clarity. The new path structure logically groups assets by blog post, and the image file is in place at the expected location.


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 and usage tips.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • In google-app-script-drug-search-app/index.mdx, the updated heroImage uses single quotes while the surrounding frontmatter fields use double quotes; consider aligning the quoting style within each file for consistency.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In `google-app-script-drug-search-app/index.mdx`, the updated `heroImage` uses single quotes while the surrounding frontmatter fields use double quotes; consider aligning the quoting style within each file for consistency.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@pharmacist-sabot pharmacist-sabot merged commit 119cbd5 into main Dec 31, 2025
10 checks passed
@pharmacist-sabot pharmacist-sabot deleted the refactor/blog-images branch December 31, 2025 06:30
github-actions bot pushed a commit that referenced this pull request Dec 31, 2025
## [1.2.2](v1.2.1...v1.2.2) (2025-12-31)

### ♻️ Refactoring

* remove and rename images to blog content ([#6](#6)) ([119cbd5](119cbd5))
@github-actions
Copy link

🎉 This PR is included in version 1.2.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant