Start with the repository's README, build instructions, and any project-specific contribution guide. Requirements differ across the studio's Linux distribution, desktop apps, and games.
Search existing issues first. For a bug, include the app version or commit, operating system, steps to reproduce, expected behavior, and what happened instead. Include relevant hardware when the problem involves graphics, audio, or local models.
For a feature, explain the problem and the workflow it would improve. Discuss substantial changes in an issue before investing in a large implementation.
Remove credentials, private files, and personal data from logs and screenshots. Report potential vulnerabilities privately using the repository's security policy.
- Create a focused branch from the current default branch.
- Follow the project's existing style and build instructions.
- Run checks relevant to the change and update affected documentation.
- Open a pull request explaining the problem, the resulting behavior, and how you verified it.
Separate automated test results from manual checks. State what remains untested, especially hardware, packaging, installation, or streaming behavior. For visible changes, include a screenshot or short recording when useful.
Keep generated build output, credentials, and unrelated changes out of the pull request. Preserve existing licenses and third-party notices; identify the source and license of any new assets or dependencies.