|
Download .github/pull_request_template.md from SaylorTwift/openhands: direct link, hf CLI and curl.
- Browser
- Download file 1.92 kB
-
https://huggingface.co/SaylorTwift/openhands/resolve/main/.github/pull_request_template.md
- Command line
-
hf download hf://SaylorTwift/openhands/.github/pull_request_template.md
-
curl -L -o pull_request_template.md https://huggingface.co/SaylorTwift/openhands/resolve/main/.github/pull_request_template.md
1.92 kB
| <!-- Keep this PR as draft until it is ready for review. --> | |
| HUMAN: | |
| <!-- Human contributors: add a short note about your testing. --> | |
| --- | |
| AGENT: | |
| <!-- AI/LLM agents: | |
| Do not edit the HUMAN section. | |
| Write a concise summary of what changed and link any reviewer artifacts, such | |
| as files under `.pr/`. For HTML artifacts, include a rendered preview link: | |
| https://htmlpreview.github.io/?https://github.com/<owner>/<repo>/blob/<branch>/.pr/<file>.html | |
| In this AGENT section and the template fields below, provide evidence that the | |
| code runs properly end-to-end. Just running unit tests is NOT sufficient. Explain | |
| exactly what command you ran and include logs, screenshots, or reproduction notes. | |
| --> | |
| ## Why | |
| <!-- Describe problem, motivation, etc. --> | |
| ## Summary | |
| <!-- 1-3 bullets describing what changed. --> | |
| - | |
| ## Issue Number | |
| <!-- Required. The linked issue must carry the `ready-for-dev` label, which | |
| means it has clear acceptance criteria (and, for bugs, reproduction evidence). | |
| If no such issue exists yet, open one using the Bug or Feature Request template | |
| and wait for it to be labeled `ready-for-dev` before opening this PR. --> | |
| Fixes # | |
| ## How to Test | |
| <!-- | |
| Required. Share the steps for the reviewer to be able to test your PR. e.g. You can test by running `npm install` then `npm build dev`. | |
| If you could not test this, say why. | |
| --> | |
| ## Video/Screenshots | |
| <!-- | |
| Provide a video or screenshots of testing your PR. e.g. you added a new feature to the gui, show us the video of you testing it successfully. | |
| For bug fixes: reproduction evidence is required. Show the bug reproduced (the | |
| error state) and then the result after your fix. A terminal screenshot or video | |
| is fine for non-UI bugs. | |
| --> | |
| ## Type | |
| - [ ] Bug fix | |
| - [ ] Feature | |
| - [ ] Refactor | |
| - [ ] Breaking change | |
| - [ ] Docs / chore | |
| ## Notes | |
| <!-- Optional: migrations, config changes, rollout concerns, follow-ups, or anything reviewers should know. --> | |