Skip to content

Refresh homepage projects section#3

Open
sedge-bot wants to merge 1 commit into
fielding:mainfrom
sedge-bot:refresh-homepage-projects-rebased
Open

Refresh homepage projects section#3
sedge-bot wants to merge 1 commit into
fielding:mainfrom
sedge-bot:refresh-homepage-projects-rebased

Conversation

@sedge-bot
Copy link
Copy Markdown

Summary

  • Rebase the homepage Projects refresh onto current main
  • Keep the updated featured project set: Thinktax, nit, Specter, Bleeping Weather, and Apprentice
  • Supersedes conflicting PR Refresh homepage projects section #1 without changing its product decision

Verification

  • npm run build
  • git diff --check origin/main..HEAD

Note: npm run check still reports pre-existing type/JS diagnostics on current main in Experience.svelte, Now.svelte, and +layout.svelte; this branch only touches Projects.svelte.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 4, 2026

Deploy Preview for fielding ready!

Name Link
🔨 Latest commit b7360a1
🔍 Latest deploy log https://app.netlify.com/projects/fielding/deploys/69f7f7f3d1bb1c0008d479b9
😎 Deploy Preview https://deploy-preview-3--fielding.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@sedge-bot
Copy link
Copy Markdown
Author

Heartbeat re-verification for PR #3 at b7360a1:

  • gh pr view 3 --json state,mergeStateStatus,mergeable,statusCheckRollup,headRefOid => OPEN, MERGEABLE, CLEAN; Netlify deploy context is still SUCCESS.
  • git fetch origin main --prune passed.
  • npm run build passed.
  • git diff --check origin/main..HEAD passed.
  • npm run check still reports the known pre-existing site Svelte/TypeScript errors in Experience.svelte, Now.svelte, and +layout.svelte; those are outside this homepage-refresh diff and are covered separately by PR Fix Svelte diagnostics in homepage sections #4.
  • Clone status stayed clean.

No duplicate PR opened; this remains ready for maintainer review/merge, with the remaining gate being merge permission/decision rather than branch freshness or buildability.

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