This guide will help you get started with the project and make your first contribution. We’re excited to welcome developers, designers, and testers of all levels.
- ✨ Ways to Contribute
- 🔍 How to Find Suitable Issues
- 🚨 Mandatory Contribution Rules
- 📝 Issue Guidelines
- 🌟 How to Submit a Contribution / PR
- 📜 Code of Conduct
- 💬 Support
- ⚖ License
- 🐛 Report bugs by opening an issue
- 💡 Suggest new features or enhancements
- 📖 Improve documentation (README, comments, examples)
- 🔧 Submit code for bugs, features, or unit tests
- ⚙️ Write GitHub workflows to improve CI/CD
- ✅ Test the app and share feedback
- Look for issues with
easy,beginner, orlevel-1tags and ask to be assigned. - Use PrivGPT Studio yourself and create your own issues for bugs, improvements, or feature suggestions.
GitHub will automatically show templates when you:
- create a new Issue
- open a Pull Request
You must follow the template structure exactly
Template links (for reference):
- Issue Templates: https://github.com/Rucha-Ambaliya/PrivGPT-Studio/tree/main/.github/ISSUE_TEMPLATE
- PR Template: https://github.com/Rucha-Ambaliya/PrivGPT-Studio/blob/main/.github/PULL_REQUEST_TEMPLATE.md
If the template does not appear for any reason:
- Manually copy and paste the template
- Fill in all required sections
- Follow the title convention and section skeleton
Issues will not be assigned and Pull Requests will not be reviewed or merged if:
- templates are missing,
- the title format is not followed, or
- the required structure is ignored.
Never commit the following files:
package.jsonpackage-lock.jsonrequirements.txt
These files often cause dependency conflicts and deployment failures.
Any PR containing them will be requested for changes or closed.
When reporting a bug, please include:
- Steps to reproduce the issue
- Expected behavior
- Actual behavior
- Screenshots or logs (if applicable)
When suggesting a feature, please include:
- Why this feature would be helpful
- Examples, references, or mockups (if possible)
Do not create a public issue for sensitive security bugs or vulnerabilities.
Instead, please report them privately by emailing me at ruchaambaliya@gmail.com.
Before you begin, make sure you have the following installed:
✅ Git
✅ Node.js (v18+)
✅ Python (3.9+)
✅ pip (Python package manager)
✅ (Optional) Ollama locally for testing local models.
-
⭐ Star this repository.
-
🍴 Fork this repository.
-
📥 Clone your fork:
git clone https://github.com/<your-github-username>/PrivGPT-Studio.git cd PrivGPT-Studio -
Set up the project (if not done already) by following instructions in Getting Started
-
🔗 Set upstream to the main repo:
git remote add upstream https://github.com/Rucha-Ambaliya/PrivGPT-Studio.git -
🌿 Create a new branch:
git checkout -b <your_branch_name>Name branch like:
- feat/cross-reference-feature
- fix/image-upload-bug
- docs/update-readme
- test/add-unit-tests-for-api
- chore/improve-ci-workflow
-
✏️ Make your changes.
-
📝 Stage and commit:
git add <changed_files> git commit -m "<your_commit_message>" -
🚀 Push your branch:
git push origin <your_branch_name> -
🔄 Open a Pull Request on GitHub.
Before creating a Pull Request Make sure your branch is up to date with the latest changes from the upstream main branch:
git checkout main git pull upstream main git checkout <your_branch_name> git merge main -
🎉 Congratulations! you've made your contribution.
If you have other questions, need help, or want to start a discussion about PrivGPT Studio,
please join our Discord Server.
💡 We’d love to hear your ideas, feedback, and suggestions there!
We are committed to creating a welcoming and inclusive environment for everyone. Please be respectful, inclusive, and considerate in all interactions.
By participating in this project, you agree to follow our Code of Conduct.
If you witness or experience unacceptable behavior, please report it privately via ruchaambaliya@gmail.com.
This project is licensed under the PolyForm Noncommercial License 1.0.0. Make sure to review and comply with the license terms.