Add Stargazers and Forkers #358
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for delightful-chaja-870050 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
❌ Deploy Preview for glassyui failed. Why did it fail? →
|
✅ Deploy Preview for delightful-chaja-870050 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@Jaishree2310 Kindly Review the PR |
|
@Jaishree2310 add the labels and assign the task |
|
@Jaishree2310 kindly assign the labels on this PR "GSSOC" AND "HACKTOBERFEST" |
|
@Jaishree2310 assign the correct level as mentioned on the main page (LEVEL 3) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes: #341
Description
The bug involves missing information on the project’s GitHub repository page, specifically the counts for "Stargazers" and "Forks," which are not displayed in the README. These metrics are crucial as they provide potential contributors and users with insights into the repository's popularity and community involvement. To reproduce this issue, navigate to the project’s GitHub repository and observe that there are no indicators for the number of stars or forks in the README, even though these counts are visible on GitHub's repository header. The expected behavior is for these metrics to be readily visible on the main README page, offering a quick view of the project’s engagement level. A solution to this is to add "Stargazers" and "Forks" badges in the README, which can be done through Shields.io. Adding these badges will allow visitors to quickly assess the project’s popularity and improve overall engagement with the repository.
Issue Reference : #341
Screenshot:
