Skip to content

New pull request made without force push#60

Merged
akash-kumar-dev merged 4 commits intobrowseping:mainfrom
Parwathi-Jayaram:new
Jan 22, 2026
Merged

New pull request made without force push#60
akash-kumar-dev merged 4 commits intobrowseping:mainfrom
Parwathi-Jayaram:new

Conversation

@Parwathi-Jayaram
Copy link
Contributor

Description

I have created a new pull request without using force push in a new branch.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Code refactoring
  • Performance improvement
  • UI/UX improvement
  • Content update
  • Chore/maintenance

Related Issue

Closes #44

Testing Done

Please describe how you tested your changes:

  • Tested in development mode (npm run dev)
  • Tested production build (npm run build && npm start)
  • Tested on multiple browsers (list them)
  • Tested on mobile devices/responsive design
  • Ran linting (npm run lint)
  • Checked for console errors

Screenshots (if applicable)

image

Checklist

IMPORTANT: Please ensure all items are checked before submitting. PRs that don't follow these guidelines may be closed.

  • I have read and followed all guidelines in CONTRIBUTING.md
  • I have used the correct branch naming convention (feature/, fix/, docs/, etc.)
  • My commits follow Conventional Commits format (feat:, fix:, docs:, etc.)
  • I have performed a self-review and tested my changes thoroughly
  • CRITICAL: I confirm ONLY my intended changes are included (no unrelated changes, debug code, or breaking changes)
  • I have updated relevant documentation if needed
  • I have tested the production build locally
  • My changes are responsive and work on mobile devices

Additional Notes

Any additional information that would be helpful for reviewers?


Remember: Quality over quantity. A well-tested, properly documented small PR is better than a large, rushed contribution.

For more details, please refer to our Contributing Guidelines.

@vercel
Copy link

vercel bot commented Jan 21, 2026

@Parwathi-Jayaram is attempting to deploy a commit to the Akash Kumar's projects Team on Vercel.

A member of the Team first needs to authorize it.

@Parwathi-Jayaram
Copy link
Contributor Author

@akash-kumar-dev I have created a new pull request this time so please check that out. I am also closing the old PR.

@vercel
Copy link

vercel bot commented Jan 22, 2026

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

Project Deployment Review Updated (UTC)
web Ready Ready Preview, Comment Jan 22, 2026 4:21pm

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the home page Features carousel auto-scroll behavior and refreshes a few NPM lockfile entries.

Changes:

  • Refactors FeaturesSection auto-scroll into a restartable interval (and updates the delay to 10s).
  • Resets auto-scroll when users manually navigate (next/prev/dots).
  • Updates package-lock.json dependency resolutions (e.g., js-yaml, tar) and aligns the recorded TypeScript spec with package.json.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 4 comments.

File Description
src/components/home/FeaturesSection.tsx Refactors carousel auto-scroll interval management and resets it on manual navigation.
package-lock.json Updates lockfile metadata and some resolved transitive dependency versions.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 112 to 115
intervalRef.current = setInterval(() => {
setCurrentIndex((prev) => (prev + 1) % features.length);
};
}, 10000);
}, [features.length]);
Copy link

Copilot AI Jan 22, 2026

Choose a reason for hiding this comment

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

This change introduces new auto-scroll timing/reset behavior (clearing/restarting an interval on navigation). Please add/extend a Vitest + Testing Library test that uses fake timers to assert (1) the slide advances after the configured interval and (2) clicking next/prev resets the timer so multiple intervals don’t accumulate.

Copilot uses AI. Check for mistakes.
Copy link
Member

Choose a reason for hiding this comment

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

@Parwathi-Jayaram, you can ignore this.

@akash-kumar-dev
Copy link
Member

Please address the formatting issues suggested by Copilot. After that, the PR looks good to merge.

@Parwathi-Jayaram
Copy link
Contributor Author

okie @akash-kumar-dev I will do that

@Parwathi-Jayaram
Copy link
Contributor Author

@akash-kumar-dev pls check it out

@akash-kumar-dev
Copy link
Member

Have fixed the remaining code formatting issues, and everything looks good now. Thanks for your contribution! Join our Discord server: https://discord.gg/Gtv9PFgaHZ

@akash-kumar-dev akash-kumar-dev merged commit 78e7fa8 into browseping:main Jan 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] The auto scroll timings in home page is too fast

2 participants

Comments