ci(mergify): upgrade configuration to current format - #13
Closed
mergify[bot] wants to merge 58 commits into
Closed
Conversation
- Replace PORTAL and LET'S TALK nav buttons with award-level animated versions - Add liquid fill, shimmer, dark sweep, and ArrowUpRight icon interactions - Fix button sizing, font sizes, and text rendering - Update Hero stats row, eyebrow label, remove ProjectsTicker - Redesign FeaturedWork with 5 Sri Lankan business projects and improved modal - Improve Services modal with 2x2 deliverables grid and single lead paragraph - Add favicon and update page title in index.html - Refine Pageloader progress bar with glow effect Co-Authored-By: claude-flow <ruv@ruv.net>
- Apply #8c8c96 grey to dominate/build/success/iconic headings across Services, Process, Footer, ContactModal - Replace CSS progress bar in Pageloader with framer-motion animated bar + shimmer dot - Fix favicon to use existing ardent-logo.svg Co-Authored-By: claude-flow <ruv@ruv.net>
- Navbar: award-level PORTAL & LET'S TALK buttons with framer-motion animations - Hero: stats row replaced with CSS grid layout - FeaturedWork: modal always centered, responsive image aspect ratio Co-Authored-By: claude-flow <ruv@ruv.net>
Remove introductory content and instructions for running the app.
Introduce a full-featured Ardeno AI assistant (ArdenoAIWidget) with GROQ API integration, localStorage conversation persistence, and UI/UX styles; add new pages and components (AboutPage, DocsPage, FAQPage, OurStory, CookieBanner, cookies helpers, trackUtm, analytics util) and public assets (logos, loader). Update App.tsx to lazy-load OurStory, remove the about route handling, preload new chunks, and always render the cookie banner; tweak ardeno-ai-context pricing copy. Also update .env (GROQ key changed), .gitignore (add .vercel), index.html and vite.config.ts. These changes wire up the new AI assistant and documentation pages and adjust app routing and persistence. Co-Authored-By: Suven Seoras <suven.20250747@iit.ac.lk> Co-Authored-By: SuvenSeoras <256380629+SuvenSeoras@users.noreply.github.com>
Restore Case Study History and Clean Assets
API key was leaking in browser network logs because it was stored as a VITE_ prefixed env var (bundled into client JS) and called directly from the browser. Adds a /api/chat serverless function that proxies requests to Groq using a server-only GROQ_API_KEY env var. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Removes the extra font imports and design token variables that were accidentally committed and broke the site's typography. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
# Vercel Speed Insights Implementation
## Summary
Successfully installed and configured Vercel Speed Insights for the Ardeno Studio website following the latest official Vercel documentation.
## What Was Implemented
### 1. Package Installation
- Installed `@vercel/speed-insights` package using npm
- Updated package.json with the new dependency
- Updated package-lock.json to ensure consistent dependency resolution
### 2. Component Integration
- Added SpeedInsights component import to App.tsx from `@vercel/speed-insights/react`
- Placed the `<SpeedInsights />` component at the root level of the application
- The component is positioned right before the closing div of the main App component
### 3. Files Modified
- **App.tsx**: Added import statement and SpeedInsights component
- Import: `import { SpeedInsights } from '@vercel/speed-insights/react';`
- Component placement: Added at the end of the JSX return statement
- **package.json**: Added @vercel/speed-insights to dependencies
- **package-lock.json**: Updated with new dependency tree
## Implementation Details
The implementation follows the official Vercel Speed Insights documentation for React applications:
- Retrieved latest installation instructions from https://vercel.com/docs/speed-insights/quickstart
- Used the React-specific integration path (`@vercel/speed-insights/react`)
- Integrated the component at the application root level in App.tsx for global coverage
## Verification
All verification steps completed successfully:
✅ TypeScript type checking passed (npm run typecheck)
✅ Production build completed successfully (npm run build)
✅ No errors or warnings introduced
✅ Lock file properly updated
## Next Steps
After deployment to Vercel:
1. Enable Speed Insights in the Vercel dashboard
2. Monitor performance metrics in the Speed Insights section
3. The component will automatically collect and send Core Web Vitals data
## Technical Notes
- The SpeedInsights component is lightweight and will only activate when deployed on Vercel
- In local development, the component is inactive and won't affect performance
- The component automatically tracks Core Web Vitals: LCP, FID, CLS, FCP, TTFB, and INP
- No additional configuration is required for basic functionality
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
…insights-m2ahvr Install Vercel Speed Insights
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
❌ Deploy Preview for ardenostudio failed.
|
Author
|
Tick the box to add this pull request to the merge queue (same as
|
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
3 participants
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.
Hey there! 👋
We've noticed that your Mergify configuration is using some deprecated fields.
No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.
Do not procrastinate! You must upgrade your configuration before 2026-09-30, otherwise your configuration will stop working.
What's Changed?
queue_rules → commit_message_template: Thecommit_message_templatesetting is deprecated. Use the declarativecommit_message_formatinstead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template (deadline: 2026-09-30)Why This Matters
Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.
Got Questions? We've Got Answers! 🙌
Is this update safe to merge?
Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!
Do I need to do anything special after merging?
Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.
What if I run into issues or have concerns?
We're here to help! Feel free to reach out to our support team anytime.
Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.
Happy merging! 🎉