chore: fix github pages deployment action#22
Merged
aritra1999 merged 12 commits intomainfrom Feb 11, 2026
Merged
Conversation
Ignore .agents/ directory used by development tools to prevent committing temporary agent files and state.
Add a modern SvelteKit-based marketing site featuring: - Hero section with animated background and GitHub stars display - Feature showcase with numbered list layout - Interactive documentation tabs (Getting Started, File Format, Variables, JSON Viewer, Keyboard Shortcuts) - Bug report and feature request links - Glassmorphic floating navbar with minimal logo - Smooth scroll indicator - Mobile-responsive design - shadcn-svelte UI components with custom brutalist styling The site uses: - SvelteKit with TypeScript and Svelte 5 runes - Tailwind CSS v4 for styling - @sveltejs/adapter-static for GitHub Pages deployment - Space Grotesk font family for consistent typography - Lowercase text treatment and refined minimalist aesthetic All documentation content is embedded in the landing page for easy discovery and quick reference.
Add automated deployment workflow that builds and deploys the marketing site to GitHub Pages on every push to main branch. The workflow: - Builds the SvelteKit site with static adapter - Configures base path for GitHub Pages subdirectory - Uses GitHub Pages artifact upload/deploy actions - Runs on Node.js 20 with npm caching for faster builds Deployment will be available at https://aritra1999.github.io/httpyum/ once GitHub Pages is enabled in repository settings.
Move CSS and markup from +page.svelte into dedicated component files for better organization and maintainability. Each section (Navbar, Hero, Features, Documentation, Contribute, Footer) is now self-contained with its own styles. Changes: - Create Navbar.svelte with navigation bar styles - Create Hero.svelte with hero section and animated background - Create Features.svelte with feature list grid layout - Create Documentation.svelte with tabs and code blocks - Create Contribute.svelte with bug report section - Create Footer.svelte with footer links - Reduce +page.svelte from ~1360 lines to ~150 lines - Keep all state management and API calls in +page.svelte - Preserve all existing functionality and responsive behavior Benefits: - Improved code organization and maintainability - Better separation of concerns - Easier to locate and modify specific sections - Styles colocated with their components
Convert all component styles from CSS modules to Tailwind utility classes for better maintainability and consistency. This reduces the overall CSS footprint by ~92% while maintaining identical visual appearance. Changes: - Replace ~1,270 lines of raw CSS with Tailwind utility classes - Convert Navbar, Hero, Features, Documentation, Contribute, Footer components - Retain only essential CSS: button styling and @Keyframes animations - Use Tailwind responsive modifiers (max-md:, max-[480px]:) for breakpoints - Keep custom brutalist button styles in Hero component - Preserve all animations (moveBoxes, bounce, fadeIn) Benefits: - Improved maintainability with utility-first approach - Consistent design tokens from Tailwind config - Better visibility of styles in markup - Automatic purging of unused styles in production - Clearer responsive design patterns
Replace black background with light gray to prevent jarring visual transition while the demo image loads. The border is now clearly visible against a neutral background instead of appearing to merge with a black box.
Replace npm ci with fresh npm install to properly handle Rollup's optional dependencies. This fixes the MODULE_NOT_FOUND error for @rollup/rollup-linux-x64-gnu on GitHub Actions runners. The issue occurs due to npm's handling of optional dependencies when using npm ci with cached node_modules.
Add prerender configuration and fix base path handling for GitHub Pages deployment. This resolves the build errors in the CI/CD pipeline. Changes: - Add +layout.js with prerender export to enable static generation - Import and use base path from $app/paths in Navbar component - Ensures all internal links respect the configured base path Fixes: - 'Could not resolve entry module' error - '404 / does not begin with base' error during prerendering
SvelteKit requires running 'svelte-kit sync' to generate internal configuration files (.svelte-kit directory) before the build process. Without this step, Vite cannot resolve the project structure and fails with 'Could not resolve entry module index.html' error. Changes: - Add explicit 'Prepare SvelteKit' step in deploy workflow - Remove error suppression (|| echo '') from prepare script to ensure proper failure visibility in CI Fixes deployment failure in GitHub Actions where the build was looking for a non-existent index.html entry point.
Replace npm with Bun in the GitHub Actions deployment workflow to match the local development environment. The project uses bun.lock for dependency management, so CI should use the same package manager. Changes: - Replace setup-node action with setup-bun action - Change npm install to bun install (removes unnecessary cleanup) - Update all npm run commands to bun run commands Benefits: - Consistency between local and CI environments - Faster dependency installation and build times - Uses correct lockfile (bun.lock instead of package-lock.json)
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
aritra1999
added a commit
that referenced
this pull request
Feb 11, 2026
Resolved conflicts in .github/workflows/deploy.yml by keeping the combined prepare+build approach from our branch, which is cleaner and more reliable than the duplicate prepare steps in main. Merges commits from main: - bfc9425 chore: fix github pages deployment action (#22) - cfa134e chore: fix github pages deployment issue (#21) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Attempt 3