mirror of
https://github.com/clash-verge-rev/clash-verge-rev.git
synced 2026-10-22 10:53:36 +08:00
18 lines
837 B
Markdown
18 lines
837 B
Markdown
## Problem
|
|
|
|
What breaks or what is missing. Product bug fixes and features require a
|
|
pre-existing issue; link it here (`Fixes #123` only when this PR fully resolves
|
|
it). Maintenance work (such as chore, perf, docs, refactor, test, CI/build,
|
|
dependency, style, routine localization, or release changes) does not require
|
|
an issue link; link one when it defines the scope. For reverts, link the PR or
|
|
commit being reverted. For security-sensitive fixes that cannot be tracked
|
|
publicly, follow maintainer-approved private tracking.
|
|
|
|
## Approach
|
|
|
|
Why this change solves the problem — the reasoning behind the approach, not a restatement of the diff.
|
|
|
|
## Scope
|
|
|
|
What changed. If anything outside the core fix was touched, explain why it was necessary. New tests are not expected by default — if any were added, justify why each is needed.
|