mirror of
https://github.com/spice2x/spice2x.github.io.git
synced 2026-08-02 06:40:42 -07:00
Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| be37865b74 | |||
| 5bce47e487 |
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user