Discover and explore README files from GitHub repositories. Search by keywords, browse trending projects, and dive deep into documentation. Search for repositories by name, topic, or technology. Click on any repository to view its README file with full markdown rendering and syntax highlighting.
- 🔍 Search GitHub repositories by name, topic, or technology
- 📄 View README files with full markdown rendering and syntax highlighting
- 🏷️ Keyword suggestions for popular and trending topics
- 🌗 Light/Dark mode for comfortable reading
- ⚡ Fast and modern UI powered by React, Vite, and Tailwind CSS
-
Clone the repository:
git clone https://github.com/your-username/github-readme-search.git cd github-readme-search -
Install dependencies:
npm install
-
Start the development server:
npm run dev
The app will be available at http://localhost:5173 (or the port shown in your terminal).
To build the app for production:
npm run buildThe output will be in the dist folder. You can preview the production build locally with:
npm run preview- No API key required: All features use the public GitHub API. Unauthenticated requests are subject to GitHub's rate limits (60 requests/hour per IP). If you hit the rate limit, please wait and try again later.
- Markdown rendering: README files are rendered with full markdown support and syntax highlighting for code blocks.
We welcome contributions from the community! If you have ideas for new features, bug fixes, or improvements, please contribute.
- Fork the repository on GitHub.
- Clone your fork locally:
git clone https://github.com/JumpStartFlows/GitReader.git cd GitReader - Create a new branch for your feature or fix:
git checkout -b your-feature-branch
- Make your changes and commit them with clear messages.
- Push your branch to your fork:
git push origin your-feature-branch
- Open a Pull Request (PR) from your branch to the
mainbranch of this repository. Please describe your changes and reference any related issues.
- Please keep your code clean and follow the existing style.
- For major changes, open an issue first to discuss what you would like to change.
- Make sure to test your changes before submitting a PR.
Thank you for helping make GitReader better!