Conversation
Align the SDK PR template with the upstream OpenHands format to keep contribution workflow consistent. Made-with: Cursor
There was a problem hiding this comment.
Pull request overview
Updates the repository’s pull request template to match the upstream OpenHands PR template format for more consistent contribution workflows.
Changes:
- Replaced the existing PR template with an upstream-aligned structure (Why/Summary/Issue/How to Test/Type/Notes).
- Updated contributor prompts and checklists to reflect the new standard.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Summary | ||
|
|
||
| [fill in a summary of this PR] | ||
|
|
||
| - | ||
|
|
There was a problem hiding this comment.
Line 16 is an empty Markdown list item (-) under “## Summary”, which will render as a blank bullet and looks accidental. Remove it or replace it with a real placeholder (e.g., an HTML comment prompt).
|
|
||
|
|
||
|
|
||
|
|
||
| - [ ] A human has tested these changes. |
There was a problem hiding this comment.
There are several whitespace-only lines (e.g., lines 3, 11, 15, 19, 23, 27, 39). Trailing spaces in Markdown can create unintended formatting (hard line breaks) and adds noise to diffs; consider trimming these to truly blank lines.
There was a problem hiding this comment.
@copilot apply changes based on this feedback
|
[Automatic Post]: It has been a while since there was any activity on this PR. @kushalsai-01, are you still working on it? If so, please go ahead, if not then please request review, close it, or request that someone else follow up. |
| - [ ] If there are instructions on how to run the code, have you followed the instructions and made sure that it works? | ||
| - [ ] If the feature is significant enough to require documentation, is there a PR open on the OpenHands/docs repository with the same branch name? | ||
| - [ ] Is the github CI passing? | ||
|
|
There was a problem hiding this comment.
If there are no Notes, maybe we can remove the Notes section entirely?
This PR updates the SDK pull request template to match the upstream OpenHands repository format.
Why
Keeping the PR template aligned with upstream ensures consistency in contribution workflows, reduces reviewer friction, and standardizes expectations across repositories.
What’s changed
Impact