Skip to content

fix: correct Keploy VSCode extension link#320

Open
Gagan202005 wants to merge 5 commits intokeploy:mainfrom
Gagan202005:fix-vscode-extension-link
Open

fix: correct Keploy VSCode extension link#320
Gagan202005 wants to merge 5 commits intokeploy:mainfrom
Gagan202005:fix-vscode-extension-link

Conversation

@Gagan202005
Copy link
Copy Markdown
Contributor

📝 Description

This PR fixes the incorrect VSCode extension link on the Keploy blog website.

The previous link was either broken or pointing to an incorrect resource. This update ensures that users are redirected to the correct official Keploy VSCode extension page.


🔗 Related Issue

Fixes: #keploy/keploy#3737


✅ Changes Made

  • Updated the VSCode extension link to the correct official link
  • Verified that the link redirects properly
  • Ensured consistency with Keploy official resources

🧪 Testing Done

  • Verified the updated link opens correctly
  • Confirmed there are no broken links
  • Checked rendering on local development server

Demo

Screen.Recording.2026-02-08.at.2.35.39.PM.mov

📋 Checklist

  • I have tested these changes locally
  • My code follows the project's coding standards
  • I have checked for broken links or regressions
  • This PR fixes only the intended issue
  • I have read the contribution guidelines

Signed-off-by: Gagan202005 <gagansinghal2005@gmail.com>
Copilot AI review requested due to automatic review settings February 8, 2026 09:13
Copy link
Copy Markdown
Contributor

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

This PR corrects the Keploy VS Code Marketplace URL in the website footer so users land on the intended extension page.

Changes:

  • Updated the footer “VS Code Extension” link to the correct Marketplace URL (removed trailing slash).

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

Copy link
Copy Markdown
Contributor

@Achanandhi-M Achanandhi-M left a comment

Choose a reason for hiding this comment

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

LGTM

@Gagan202005
Copy link
Copy Markdown
Contributor Author

Hey @amaan-bhati,
This PR has been approved by @Achanandhi-M. Please go ahead and merge it when you get a chance. Thanks!

@dhananjay6561
Copy link
Copy Markdown
Contributor

Hi @Gagan202005
Thanks for working on this and submitting the PR. The changes look good and the implementation addresses the issue well.
The review has been completed and everything checks out on our end. We appreciate the effort you’ve put into this contribution.

This PR will be merged shortly. Thanks again for contributing!

@kilo-code-bot
Copy link
Copy Markdown

kilo-code-bot bot commented Mar 24, 2026

Code Review Summary

Status: No Changes to Review | Recommendation: Close PR

Observations

This PR was originally intended to fix the VSCode extension link in components/footer.tsx by removing a trailing slash. However, upon incremental review:

  • PR diff is empty - The GitHub API reports 0 file changes, 0 additions, and 0 deletions
  • The PR branch (fix-vscode-extension-link) has been synchronized with main
  • There are no net code changes to merge

Previous Review Context

The previous review at commit 60324c95d792cf73aa27e171c342e4e1575ed377 also noted the empty diff status. Since then, no new changes have been introduced to this PR.

Recommendation

This PR should be closed without merging since:

  1. There are no effective code changes to apply
  2. The fix may have already been applied to main through another means
  3. Merging an empty PR would add no value

The maintainers should verify that the VSCode extension link is already correct in the current main branch before closing.

Files Reviewed (0 files)

No files with changes.


Reviewed by claude-4.5-opus-20251124 · 1,144,494 tokens

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.

6 participants