Compare commits

...

2 Commits

Author SHA1 Message Date
sp2xdev be37865b74 Update issue templates 2024-08-04 00:25:48 -07:00
sp2xdev 5bce47e487 Update CONTRIBUTING.md 2024-07-28 22:57:33 -07:00
2 changed files with 5 additions and 3 deletions
+4 -3
View File
@@ -16,9 +16,10 @@ assignees: ''
## Laptop
*Are you running this on a laptop? Does it have a hybrid iGPU+ dGPU configuration?*
## Describe the issue
*what's the issue?*
## Attached log.txt file, if available
> [!WARNING]
> Please make sure you remove any personally identifiable information from the log file.
## Describe the issue
*what's the issue?*
> Please set `-loglevel` to `all` before launching the game for more verbose logs.
+1
View File
@@ -31,3 +31,4 @@ Lastly, watch out for legacy OS compatibility. Currently, the minimum support fl
* Do not make code changes in unrelated areas; i.e., do not run code linters and auto-formatters for parts of the code that you didn't modify.
* Note: there are no strict rules for code formatting, but please attempt to emulate the style around the code you are modifying.
* Try to submit smaller chunks of code, instead one gigantic patch. For example, don't submit a patch for "Improve feature XYZ"; instead, submit "Change how A works to prepare for feature XYZ" "Refactor B for feature XYZ" "Add feature B to enable feature XYZ".
* Write to the log for anything useful - it helps immensely with debugging post-mortem. At the same time though, avoid spamming the log for something trivial.