First off, thank you for taking the time to contribute! This document outlines how to get started with contributing to GeForce Infinity, along with the standards and approval process required.
If this is your first time contributing:
-
Fork the repository to your own GitHub account:
https://github.com/doublegate/GeForce-Infinity/fork -
Clone your fork:
git clone https://github.com/YOUR_USERNAME/GeForce-Infinity.git cd GeForce-Infinity -
Set the original repository as an upstream remote:
git remote add upstream https://github.com/doublegate/GeForce-Infinity.git
-
Always create a new branch for your work:
git checkout -b your-feature-name
-
If your branch is a small fix simply name it. But if it's a major bugfix or new feature you must name it as fix/your-feature-name or feature/your-feature-name
-
Keep your fork up to date:
git fetch upstream git rebase upstream/main
-
Push your changes
git push origin your-feature-name
We use Prettier for formatting. You must format your code before submitting a PR.
Prettier Settings:
Default settings, but we use tab width 4.
If using VScode / VSCodium or any other fork, open Command Palette by Ctrl+Shift+P and then type Open User Settings and select option with JSON, then you can set these parameters for Prettier:
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.formatOnSave": true,
"prettier.tabWidth": 4,-
✅ Write clean, modular, and dynamic code
-
🧼 Avoid hardcoding whenever possible
-
💬 Use comments for non-trivial logic or important context
-
🚫 Avoid huge PRs – break things into smaller changes where possible
-
🧪 If applicable, add test coverage or usage examples
-
Push your branch to your fork
-
Open a Pull Request to the master branch of our repo.
-
Include a clear title and description of the changes made.
-
PR Review Requirements:
- Your PR must be approved by both:
- @doublegate
- @t0msk
If you’re unsure or want feedback before writing code:
- Write to us on Discord (linked in README) or start a discussion