mirror of
https://github.com/openclaw/openclaw.git
synced 2026-06-23 21:08:14 +00:00
4a0f497f16
* improve: simplify PR context and evidence * improve: decouple PR context from proof labels * fix: satisfy PR context lint
58 lines
1.7 KiB
Markdown
58 lines
1.7 KiB
Markdown
<!--
|
|
Optional linked context:
|
|
Add a visible `Closes #<issue-number>` or `Related: #<issue-number>` line
|
|
below this comment.
|
|
|
|
Required PR title:
|
|
type: user-facing description
|
|
Use a parenthesized scope only when it adds clarity:
|
|
fix(auth): login redirect loops when session cookie is expired
|
|
|
|
Types: feat, fix, improve, refactor, docs, chore.
|
|
For fixes, describe the user-visible symptom and trigger:
|
|
fix: task list fails to load when user has no environments
|
|
Avoid implementation details such as:
|
|
fix: add null check to task query
|
|
-->
|
|
|
|
## What Problem This Solves
|
|
|
|
<!--
|
|
Describe the concrete user, product, or operational problem.
|
|
For fixes, begin with:
|
|
"Fixes an issue where users <do X> would <experience Y> when <condition>."
|
|
or:
|
|
"Resolves a problem where..."
|
|
|
|
Name the affected UI surface or workflow. Do not describe the code-level cause here.
|
|
-->
|
|
|
|
## Why This Change Was Made
|
|
|
|
<!--
|
|
In one or two sentences, explain the complete shipped solution, key design
|
|
decisions, and relevant boundaries or non-goals. Include implementation detail
|
|
only when it helps reviewers understand user-visible behavior or risk.
|
|
Avoid file-by-file narration.
|
|
-->
|
|
|
|
## User Impact
|
|
|
|
<!--
|
|
State what users, operators, or developers can now do or expect. Lead with the
|
|
concrete benefit and use user-facing language. If there is no user-visible
|
|
impact, say so plainly.
|
|
-->
|
|
|
|
## Evidence
|
|
|
|
<!--
|
|
Show the most useful proof that this change works. Screenshots, screencasts,
|
|
terminal output, focused tests, CI results, live observations, redacted logs,
|
|
and artifact links are all useful. Include before/after evidence for visual
|
|
changes when it clarifies the result.
|
|
|
|
Reviewers will inspect the code, tests, and CI. Use this section to make the
|
|
validation easy to understand, not to restate the diff.
|
|
-->
|