Readme update - #191
Conversation
Issues fixed#90
-> Introduced `.github/labeler-issues.yml` for keyword-based issue labeling -> Added `.github/workflows/issue-labeler.yml` to automate applying labels -> Helps categorize issues as bug, enhancement, documentation, or testing without manual intervention
…entation - Add professional header with badges and navigation links - Include comprehensive table of contents for easy navigation - Add detailed feature list highlighting all widget capabilities - Expand Quick Start section with multiple usage examples - Document all 4 widget types (Ranking, Analytics, Activity Graph, Streak) - Add customization section with parameter reference table - Include complete deployment guide with step-by-step instructions - Add contributing guidelines and development setup - Include support, acknowledgments, and licensing sections - Improve overall structure and readability - Add clear examples for all features and themes This update transforms the README from a basic theme showcase into comprehensive documentation that helps users understand, deploy, and contribute to the project.
|
@JayanithaSivakumar is attempting to deploy a commit to the shivani-rajalakshmi's projects Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s public-facing documentation and adds automation to label GitHub issues based on their content, aiming to improve onboarding and project maintenance.
Changes:
- Expanded
README.mdinto a fuller set of docs (features, quick start, customization, deployment, contributing). - Added a GitHub Actions workflow to auto-label issues on open/edit.
- Added a label-regex configuration file intended for the issue labeler.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| README.md | Major documentation overhaul with usage examples, deployment steps, and contribution/support sections. |
| .github/workflows/auto-issues-labeler.yml | New workflow to automatically label issues. |
| .github/auto-issues-labeler.yml | New regex-based label configuration for the issue labeler. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| **Usage:** | ||
| ```markdown | ||
|  |
There was a problem hiding this comment.
The README documents a type query parameter (and separate widget endpoints) (e.g., type=rank on this line), but the deployed API handler (api/index.js) does not read req.query.type and always renders a single combined SVG. Either implement type handling in the API or update this section so the usage examples match the actual behavior.
|  | |
|  |
| | `type` | Widget type | `rank` | `rank`, `analytics`, `graph`, `streak` | | ||
|
|
||
| ### Advanced Customization Examples | ||
|
|
||
| #### Combining Parameters | ||
| ```markdown | ||
|  | ||
| ``` |
There was a problem hiding this comment.
Customization docs list a type parameter (and show examples using type=...), but the API currently doesn’t support type at all. This makes the parameter table and the advanced examples misleading; please remove/correct them or add type support in the API.
| git clone https://github.com/fewinfos/readme-activity-calender.git | ||
| cd readme-activity-calender |
There was a problem hiding this comment.
Deployment instructions clone https://github.com/fewinfos/readme-activity-calender.git and cd readme-activity-calender, which appears to be a different project name than this repo. This will prevent users from deploying this project; update the clone URL and directory name to match the actual repository.
| git clone https://github.com/fewinfos/readme-activity-calender.git | |
| cd readme-activity-calender | |
| git clone https://github.com/fewinfos/github-repo-readme-stats.git | |
| cd github-repo-readme-stats |
|
|
||
| If you encounter any issues or have questions: | ||
|
|
||
| - [Open an issue](https://github.com/fewinfos/readme-activity-calender/issues) |
There was a problem hiding this comment.
Support section links to fewinfos/readme-activity-calender/issues, which is a different repository and will send users to the wrong tracker. Update the issue link to point to this repository’s issues page.
| - [Open an issue](https://github.com/fewinfos/readme-activity-calender/issues) | |
| - [Open an issue](https://github.com/fewinfos/github-repo-readme-stats/issues) |
| uses: github/issue-labeler@v3 | ||
| with: | ||
| repo-token: "${{ secrets.GITHUB_TOKEN }}" | ||
| configuration-path: .github/labeler-issues.yml |
There was a problem hiding this comment.
configuration-path points to .github/labeler-issues.yml, but this PR adds .github/auto-issues-labeler.yml instead. As-is, the workflow will fail to find its config; either rename the config file to .github/labeler-issues.yml or update configuration-path to the added file.
| configuration-path: .github/labeler-issues.yml | |
| configuration-path: .github/auto-issues-labeler.yml |
| bug: | ||
| - '(?i)bug' | ||
|
|
There was a problem hiding this comment.
This labeler config file name doesn’t match the workflow’s configuration-path (.github/labeler-issues.yml). Unless the workflow is updated, this file will be unused and issue labeling won’t work; align the filename/path with the workflow configuration.
| [](LICENSE) | ||
| [](https://github.com/fewinfos/readme-activity-calender/issues) | ||
| [](https://github.com/fewinfos/readme-activity-calender/stargazers) |
There was a problem hiding this comment.
The badges/links at the top reference fewinfos/readme-activity-calender, which doesn’t match this repository (github-repo-readme-stats). This will show the wrong license/issues/stars and send users to the wrong issue tracker/stargazers page; update these badge URLs/targets to the correct repo.
| [](LICENSE) | |
| [](https://github.com/fewinfos/readme-activity-calender/issues) | |
| [](https://github.com/fewinfos/readme-activity-calender/stargazers) | |
| [](LICENSE) | |
| [](https://github.com/fewinfos/github-repo-readme-stats/issues) | |
| [](https://github.com/fewinfos/github-repo-readme-stats/stargazers) |
The README now goes from a basic themes showcase to a comprehensive, professional documentation that properly explains the project, helps users get started quickly, and encourages contributions