|
| 1 | +# Contributing to Good First Issue |
| 2 | + |
| 3 | +Thanks for your interest in contributing! This guide will help you get started. |
| 4 | + |
| 5 | +## Prerequisites |
| 6 | + |
| 7 | +Before you begin, make sure you have the following installed: |
| 8 | + |
| 9 | +- **Node.js** (v18 or later) - [Download](https://nodejs.org/) |
| 10 | +- **Python 3** - [Download](https://www.python.org/downloads/) |
| 11 | +- **Bun** - A fast JavaScript runtime and package manager. Install it with: |
| 12 | + ```bash |
| 13 | + curl -fsSL https://bun.sh/install | bash |
| 14 | + ``` |
| 15 | + Or see [bun.sh](https://bun.sh/) for other installation methods. |
| 16 | + |
| 17 | +## Project Structure |
| 18 | + |
| 19 | +Good First Issue has two main components: |
| 20 | + |
| 21 | +- **Front-end app** - Built with Nuxt.js, displays the curated list of repositories |
| 22 | +- **Data population script** - Written in Python, fetches repository data from GitHub |
| 23 | + |
| 24 | +## Setting Up Locally |
| 25 | + |
| 26 | +1. **Clone the repository** |
| 27 | + |
| 28 | + ```bash |
| 29 | + git clone https://github.com/DeepSourceCorp/good-first-issue.git |
| 30 | + cd good-first-issue |
| 31 | + ``` |
| 32 | + |
| 33 | +2. **Set up sample data files** |
| 34 | + |
| 35 | + The front-end app needs data files to display repositories. Copy the sample files to get started: |
| 36 | + |
| 37 | + ```bash |
| 38 | + cp data/generated.sample.json data/generated.json |
| 39 | + cp data/tags.sample.json data/tags.json |
| 40 | + ``` |
| 41 | + |
| 42 | + These files contain: |
| 43 | + - `generated.json` - Repository metadata (stars, issues, languages, etc.) |
| 44 | + - `tags.json` - Language tags for filtering |
| 45 | + |
| 46 | +3. **Install dependencies** |
| 47 | + |
| 48 | + ```bash |
| 49 | + bun install |
| 50 | + ``` |
| 51 | + |
| 52 | +4. **Start the development server** |
| 53 | + |
| 54 | + ```bash |
| 55 | + bun dev |
| 56 | + ``` |
| 57 | + |
| 58 | + The app will open at [http://localhost:3000](http://localhost:3000). |
| 59 | + |
| 60 | +## Running Tests |
| 61 | + |
| 62 | +To run the data sanity tests: |
| 63 | + |
| 64 | +```bash |
| 65 | +python -m pytest gfi/test_data.py |
| 66 | +``` |
| 67 | + |
| 68 | +Or using unittest directly: |
| 69 | + |
| 70 | +```bash |
| 71 | +python gfi/test_data.py |
| 72 | +``` |
| 73 | + |
| 74 | +## Making Changes |
| 75 | + |
| 76 | +1. Create a new branch for your changes |
| 77 | +2. Make your changes and test them locally |
| 78 | +3. Submit a pull request with a clear description of what you changed and why |
0 commit comments