-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[frontend]: Push to Github button should only push branch, but not creating a PR #5179
Comments
I actually disagree with this--I generally want it to open the PR. But I think adding some customizability here would be good Edit: ah I see you're proposing a second button. That seems reasonable |
We could also do some sort of checkbox? But it might be tricky to place it near the button.. Let's ask OpenHands try to implement the two button approach and see how it'd go! @openhands-agent |
A potential fix has been generated and a draft PR #5181 has been created. Please review the changes. |
… creation * Rename 'Push to GitHub' button to 'Push to Branch' * Add state to track PR creation * Show only 'Push changes to PR' button after PR is created * Update tests to reflect new behavior
…ranch, but not creating a PR (#5181) Co-authored-by: Xingyao Wang <[email protected]> Co-authored-by: Xingyao Wang <[email protected]> Co-authored-by: Graham Neubig <[email protected]>
What problem or use case are you trying to solve?
After clicking the "push to github" button, the frontend will automatically send a message asking the agent to push stuff to github AND create a PR.
Describe the UX of the solution you'd like
We should have two separate buttons for the functionality of "push to remote branch", AND, "push & create a new PR" - so we don't accidentally create new PR when not intended.
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: