fix: blog featured post

[nickytonline]

Description

Related Tickets & Documents

Steps to QA

Tier (staff will fill in)

• Tier 1
• Tier 2
• Tier 3
• Tier 4

[optional] What gif best describes this PR or how it makes you feel?

[netlify]

✅ Deploy Preview for opensauced-landing ready!

Name	Link
🔨 Latest commit	75638c2
🔍 Latest deploy log	https://app.netlify.com/sites/opensauced-landing/deploys/66e867940b87100008d3490c
😎 Deploy Preview	https://deploy-preview-365--opensauced-landing.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jpmcb]

@nickytonline - you need to rebase this since it looks like you're carrying commits over from #358

[nickytonline]

@nickytonline - you need to rebase this since it looks like you're carrying commits over from #358

Yeah, I accidentally used an old branch. 🙈 Just rebasing.

[nickytonline]

I think the GitHub UI is not reflecting my latest. Did another push force, but it still shows multiple commits here. 😅

[jpmcb]

The tip of your fix-blog-featured-post has 4 commits (including those from godsfavour1975@gmail.com:

It looks like you picked these up from your branch being based on: #357 which is also getting your force pushes and has your pizza-action commit. So you probably started from a dirty state.

You could drop those commits in an interactive rebase:

d eb65f477 fix: fixed featured post img
d 00d046da Update components/sections/blog/components/Post.tsx
d e26af92c Update components/sections/blog/FeaturedPost.tsx
pick 75638c22 chore: updated pizza action

but it'd probably just be easier to throw out this branch, pull down from main and ensure you don't have other commits

[nickytonline]

Yeah, throwing it out.

I accidentally hijacked someone's PR