gitingest/CONTRIBUTING.md
Filip Christiansen a99089ab11
Some checks are pending
CI / test (macos-latest, 3.10) (push) Waiting to run
CI / test (macos-latest, 3.11) (push) Waiting to run
CI / test (macos-latest, 3.12) (push) Waiting to run
CI / test (macos-latest, 3.13) (push) Waiting to run
CI / test (macos-latest, 3.8) (push) Waiting to run
CI / test (macos-latest, 3.9) (push) Waiting to run
CI / test (true, ubuntu-latest, 3.13) (push) Waiting to run
CI / test (ubuntu-latest, 3.10) (push) Waiting to run
CI / test (ubuntu-latest, 3.11) (push) Waiting to run
CI / test (ubuntu-latest, 3.12) (push) Waiting to run
CI / test (ubuntu-latest, 3.8) (push) Waiting to run
CI / test (ubuntu-latest, 3.9) (push) Waiting to run
CI / test (windows-latest, 3.10) (push) Waiting to run
CI / test (windows-latest, 3.11) (push) Waiting to run
CI / test (windows-latest, 3.12) (push) Waiting to run
CI / test (windows-latest, 3.13) (push) Waiting to run
CI / test (windows-latest, 3.8) (push) Waiting to run
CI / test (windows-latest, 3.9) (push) Waiting to run
CodeQL / Analyze (push) Waiting to run
Build & Push Container / docker-build (push) Waiting to run
release-please / release (push) Waiting to run
OSSF Scorecard / Scorecard analysis (push) Waiting to run
refactor: consistent cloning & pattern-handling (#388)
Co-authored-by: ix-56h <n.guintini@protonmail.com>
2025-07-23 16:35:32 +02:00

92 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Contributing to Gitingest
Thanks for your interest in contributing to **Gitingest** 🚀 Our goal is to keep the codebase friendly to first-time contributors.
If you ever get stuck, reach out on [Discord](https://discord.com/invite/zerRaGK9EC).
---
## How to Contribute (non-technical)
- **Create an Issue** found a bug or have a feature idea?
[Open an issue](https://github.com/coderamp-labs/gitingest/issues/new).
- **Spread the Word** tweet, blog, or tell a friend.
- **Use Gitingest** real-world usage gives the best feedback. File issues or ping us on [Discord](https://discord.com/invite/zerRaGK9EC) with anything you notice.
---
## How to submit a Pull Request
> **Prerequisites**: The project uses **Python 3.9+** and `pre-commit` for development.
1. **Fork** the repository.
2. **Clone** your fork:
```bash
git clone https://github.com/coderamp-labs/gitingest.git
cd gitingest
```
3. **Set up the dev environment**:
```bash
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev,server]"
pre-commit install
```
4. **Create a branch** for your changes:
```bash
git checkout -b your-branch
```
5. **Make your changes** (and add tests when relevant).
6. **Stage** the changes:
```bash
git add .
```
7. **Run the backend test suite**:
```bash
pytest
```
8. *(Optional)* **Run `pre-commit` on all files** to check hooks without committing:
```bash
pre-commit run --all-files
```
9. **Run the local server** to sanity-check:
```bash
cd src
uvicorn server.main:app
```
Open [http://localhost:8000](http://localhost:8000) to confirm everything works.
10. **Commit** (signed):
```bash
git commit -S -m "Your commit message"
```
If *pre-commit* complains, fix the problems and repeat **5 9**.
11. **Push** your branch:
```bash
git push origin your-branch
```
12. **Open a pull request** on GitHub with a clear description.
13. **Iterate** on any review feedback—update your branch and repeat **6 11** as needed.
*(Optional) Invite a maintainer to your branch for easier collaboration.*