mirror of
https://github.com/OpenHands/OpenHands.git
synced 2026-03-22 13:47:19 +08:00
43 lines
1.4 KiB
Django/Jinja
43 lines
1.4 KiB
Django/Jinja
You are requested to fix issue #{{ issue_number }}: "{{ issue_title }}" in a repository.
|
|
A comment on the issue has been addressed to you.
|
|
|
|
# Issue Body
|
|
{{ issue_body }}
|
|
|
|
# Comment
|
|
{{ issue_comment }}
|
|
|
|
{% if previous_comments %}
|
|
# Previous Comments
|
|
For reference, here are the previous comments on the issue:
|
|
|
|
{% for comment in previous_comments %}
|
|
- @{{ comment.author }} said:
|
|
{{ comment.body }}
|
|
{% if not loop.last %}
|
|
|
|
{% endif %}
|
|
{% endfor %}
|
|
{% endif %}
|
|
|
|
# Guidelines
|
|
|
|
1. Review the task carefully.
|
|
2. For all changes to actual application code (e.g. in Python or Javascript), add an appropriate test to the testing directory to make sure that the issue has been fixed
|
|
3. Run the tests, and if they pass you are done!
|
|
4. You do NOT need to write new tests if there are only changes to documentation or configuration files.
|
|
|
|
# Final Checklist
|
|
Re-read the issue title, body, and comments and make sure that you have successfully implemented all requirements.
|
|
|
|
Use the $GITHUB_TOKEN and GitHub APIs to
|
|
|
|
1. Create a new branch using `openhands/` as a prefix (e.g `openhands/update-readme`)
|
|
2. Commit your changes with a clear commit message
|
|
3. Push the branch to GitHub
|
|
4. Use the `create_pr` tool to open a new PR
|
|
5. The PR description should:
|
|
- Follow the repository's PR template (check `.github/pull_request_template.md` if it exists)
|
|
- Mention that it "fixes" or "closes" the issue number
|
|
- Include all required sections from the template
|