From be61239529c84dfd51980c479627061aa08b64ef Mon Sep 17 00:00:00 2001 From: pa Date: Mon, 16 Mar 2026 15:45:29 +0900 Subject: [PATCH] add contributing guidelines --- .github/CONTRIBUTING.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .github/CONTRIBUTING.md diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 00000000..cf06208d --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,20 @@ +# Contributing to VRCX + +Thank you for your interest in contributing to VRCX! Here are a few guidelines to help things go smoothly. + +## Before You Start + +- **Large changes require prior discussion.** If your PR involves significant new features, refactors, or architectural changes, please open an issue first to discuss the approach. PRs submitted without prior discussion may not be accepted. +- **Small fixes are always welcome.** Typo fixes, bug fixes, and minor improvements can be submitted directly. + +## Looking for Something to Work On? + +Check out issues labeled [`PR welcome`](https://github.com/vrcx-team/VRCX/issues?q=label%3A%22pr+welcome%22+is%3Aclosed) — these are contributions we'd love to see. Note that even for `PR welcome` issues, if the change involves core functionality, please discuss it in the issue first. + +## Submitting a Pull Request + +1. Fork the repository and create your branch from `master`. +2. Make your changes and test them locally. +3. Open a pull request with a clear description of what you changed and why. + +Thanks for helping make VRCX better!