Message new Branch(es) are ready to be merged #10533

New Issue

GiteaMirror · 2025-11-02T09:10:32-06:00

GiteaMirror commented

2025-11-02 09:10:32 -06:00

Originally created by @uvulpos on GitHub (Mar 27, 2023).

Feature Description

As a developer, I want the ability to create pull requests fast. Therefore, I create a branch and switch then to the UI to click the button create a pull request. To improve my workflow, I would appreciate it if there was a banner to quickly create Pull Requests, like there is on GitHub.

Notes:

these messages should only appear for really newly created Branches, e.x. 1 hour
It is available on the main page of the code repository
Example:

Screenshots

No response

Originally created by @uvulpos on GitHub (Mar 27, 2023). ### Feature Description As a developer, I want the ability to create pull requests fast. Therefore, I create a branch and switch then to the UI to click the button create a pull request. To improve my workflow, I would appreciate it if there was a banner to quickly create Pull Requests, like there is on GitHub. **Notes:** - these messages should only appear for really newly created Branches, e.x. 1 hour - It is available on the main page of the code repository - Example: ![Example Image](https://i.ytimg.com/vi/rgbCcBNZcdQ/maxresdefault.jpg) ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:10:32 -06:00

GiteaMirror closed this issue

2025-11-02 09:10:33 -06:00

GiteaMirror commented

2025-11-02 09:10:33 -06:00

@lunny commented on GitHub (Mar 27, 2023):

Do you know Gitea will return a link to the git client, so you can just click the link to enter the process to create a pull request?

@lunny commented on GitHub (Mar 27, 2023): Do you know Gitea will return a link to the git client, so you can just click the link to enter the process to create a pull request?

GiteaMirror commented

2025-11-02 09:10:33 -06:00

@yardenshoham commented on GitHub (Mar 27, 2023):

Many people use git UIs without looking the command line output when pushing so I support this

@yardenshoham commented on GitHub (Mar 27, 2023): Many people use git UIs without looking the command line output when pushing so I support this

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@wxiaoguang commented on GitHub (Mar 27, 2023):

Do you know Gitea will return a link to the git client, so you can just click the link to enter the process to create a pull request?

I never used that

@wxiaoguang commented on GitHub (Mar 27, 2023): > Do you know Gitea will return a link to the git client, so you can just click the link to enter the process to create a pull request? I never used that

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@uvulpos commented on GitHub (Mar 27, 2023):

I have to agree with @yardenshoham, I got used to the VSC Git Integration since I was kinda forced by my team to use a similar workflow and I don't have any console output for that. Thats why I need a button to do this for me 🙂

@uvulpos commented on GitHub (Mar 27, 2023): I have to agree with @yardenshoham, I got used to the VSC Git Integration since I was kinda forced by my team to use a similar workflow and I don't have any console output for that. Thats why I need a button to do this for me 🙂

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@lunny commented on GitHub (Mar 27, 2023):

I'm not against this feature but just mentioned we have another one I used it frequently. I just sent a PR to improve the documentation. #23744

@lunny commented on GitHub (Mar 27, 2023): I'm not against this feature but just mentioned we have another one I used it frequently. I just sent a PR to improve the documentation. #23744

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@delvh commented on GitHub (Mar 27, 2023):

Additionally, the problem with the existing feature is that it is only triggered on the first commit.
Oftentimes, you want to have multiple commits before creating a PR.

@delvh commented on GitHub (Mar 27, 2023): Additionally, the problem with the existing feature is that it is **only triggered on the first commit**. Oftentimes, you want to have multiple commits before creating a PR.

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@JakobDev commented on GitHub (Mar 27, 2023):

There are 2 another big problems:

As long as no error happens, most people don't take a look at the output of commands like git push, that they use very often.
If you use a Git GUI, you will most likely (depending on the GUI) see the Output of git push at all.

@JakobDev commented on GitHub (Mar 27, 2023): There are 2 another big problems: 1. As long as no error happens, most people don't take a look at the output of commands like `git push`, that they use very often. 2. If you use a Git GUI, you will most likely (depending on the GUI) see the Output of `git push` at all.

GiteaMirror commented

2025-11-02 09:10:34 -06:00

@uvulpos commented on GitHub (Mar 27, 2023):

In the JetBrains Interface, there is a git tab at the bottom, but the VSCode git extension does not have this like mentioned before :)

@uvulpos commented on GitHub (Mar 27, 2023): In the JetBrains Interface, there is a git tab at the bottom, but the VSCode git extension does not have this like mentioned before :)

GiteaMirror commented

2025-11-02 09:10:35 -06:00

@jpraet commented on GitHub (Mar 27, 2023):

Duplicate of #13196. There is a draft PR #14003

@jpraet commented on GitHub (Mar 27, 2023): Duplicate of #13196. There is a draft PR #14003

GiteaMirror commented

2025-11-02 09:10:35 -06:00

@uvulpos commented on GitHub (Mar 28, 2023):

Oh, but at least we can make it alive again :)
Over 2 years sounds dead to me

@uvulpos commented on GitHub (Mar 28, 2023): Oh, but at least we can make it alive again :) Over 2 years sounds dead to me

GiteaMirror commented

2025-11-02 09:10:35 -06:00

@lunny commented on GitHub (Mar 29, 2023):

Let's keep this one since there more discuss here. And I copied the issue content below from @kolaente

As a user, I would like to see a prompt on the home page or repository page to create a new PR if I recently pushed to a new branch for which no PR exists yet so that I save clicking on the "new PR" button on the repo page.

This could be done purely through the db without any git calls since we already have all the data in the action table.

I think we can always assume the user has the rights to create a PR if they have the right to push to a new branch in that repo, so no need to check that.
We would just need another check if the repo pushed to is a fork to check with the head repo if a PR exists there and not in the fork repo.

@lunny commented on GitHub (Mar 29, 2023): Let's keep this one since there more discuss here. And I copied the issue content below from @kolaente > As a user, I would like to see a prompt on the home page or repository page to create a new PR if I recently pushed to a new branch for which no PR exists yet so that I save clicking on the "new PR" button on the repo page. > This could be done purely through the db without any git calls since we already have all the data in the action table. > I think we can always assume the user has the rights to create a PR if they have the right to push to a new branch in that repo, so no need to check that. > We would just need another check if the repo pushed to is a fork to check with the head repo if a PR exists there and not in the fork repo.

GiteaMirror commented

2025-11-02 09:10:35 -06:00

@kolaente commented on GitHub (Apr 1, 2023):

I've rebased and fixed a bunch of things in my PR https://github.com/go-gitea/gitea/pull/14003 - would appreciate a couple of eyeballs.

@kolaente commented on GitHub (Apr 1, 2023): I've rebased and fixed a bunch of things in my PR https://github.com/go-gitea/gitea/pull/14003 - would appreciate a couple of eyeballs.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10533