mirror of
https://github.com/wailsapp/wails.git
synced 2025-05-18 18:09:30 +08:00
30 lines
1.7 KiB
Plaintext
30 lines
1.7 KiB
Plaintext
---
|
|
sidebar_position: 30
|
|
---
|
|
|
|
# 修复漏洞
|
|
|
|
The process for fixing bugs are as follows:
|
|
|
|
- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
|
|
- Before developing, check that the ticket includes the following information:
|
|
- The scope of the issue including platforms affected
|
|
- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
|
|
- The output of `wails doctor`
|
|
- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
|
|
- Comment on the ticket stating you wish to develop a fix
|
|
- Clone the repository and create a branch with the format `bugfix/<ticket_number>_<ticket_title>`
|
|
- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
|
|
- Once all the testing is completed, please update the status of the PR from draft and leave a message.
|
|
|
|
:::note
|
|
There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
|
|
bugfixes should be discussed as the approach may have unintended side effects.
|
|
::: :::
|
|
:::
|
|
|
|
:::warning
|
|
Any PRs opened without a corresponding ticket may be rejected.
|
|
::: :::
|
|
:::
|