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.
I have update the link to the homepage in the package.json file in the lib folder
Greptile Summary
Updated On: 2025-09-12 04:55:19 UTC
This PR fixes the homepage URL in the
eslint-plugin-storybook
package.json file. The change updates the homepage field fromhttps://github.com/storybookjs/storybook/code/lib/eslint-plugin#readme
tohttps://github.com/storybookjs/storybook/tree/next/code/lib/eslint-plugin#readme
.The issue with the original URL is that GitHub requires the
tree/{branch-name}
path segment to properly navigate to a specific directory within a repository. Without this, the link would not correctly resolve to the package's documentation. The fix adds/tree/next
to the URL, ensuring it points to the eslint-plugin directory in the 'next' branch where the package's README and documentation reside.This change aligns the eslint-plugin package with the URL pattern used by other Storybook packages and follows established conventions for GitHub repository links. The modification is minimal and surgical, affecting only the homepage field while preserving all other package metadata.
PR Description Notes:
Confidence score: 5/5
Context used:
Context - In the documentation, ensure that the links to the builder's documentation and the Next.js framework documentation are correct and not broken. (link)
Context - PR titles must be in the format of 'Area: Summary', with both Area and Summary starting with a capital letter. (link)