You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current UX flow when you attempt to create a Pull Request, a branch must already exist and contain changes, requiring additional steps to be made to create said pull request. It would be a nice to have to be able to create a new branch within the current UI instead of having to push a new branch with a single change to do so.
Although #11888 is similar, this request is different as the referenced issue is asking to create Pull Requests in issues, while I'm requesting the ability to create one without having an issue tied.
Closing issue because ...
Upon further use of Gitea and learning Git practices, #11888 should be sufficient enough
The text was updated successfully, but these errors were encountered:
You can create a branch from the UI, however it still won't let you open a PR if there would be no differences.
It would seem there may be a bug relating to this, as I was not prompted with UX informing me to "Create branch ... from '...'". However, although a separate potential bug, this request should still stand as you are unable to create a Pull Request with the above statement due to "These branches are equal. There is no need to create a pull request."
Reinitialized
changed the title
[FEATURE] Create branch along with Pull Request
[FEATURE] Create branch along with Pull Request without requiring existing changes
Feb 17, 2021
With the current UX flow when you attempt to create a Pull Request, a branch must already exist and contain changes, requiring additional steps to be made to create said pull request. It would be a nice to have to be able to create a new branch within the current UI instead of having to push a new branch with a single change to do so.Although #11888 is similar, this request is different as the referenced issue is asking to create Pull Requests in issues, while I'm requesting the ability to create one without having an issue tied.Closing issue because ...
Upon further use of Gitea and learning Git practices, #11888 should be sufficient enough
The text was updated successfully, but these errors were encountered: