[Proposal] A third way to do a merge

[David Martínez Labuiga]

Usually we have 2 ways of doing a merge:

1-merge command

2-pull requests

In certain projects You can stablish a hook to limit the merge command and force pull-requests.

I want to propose a third option:

3- Doing a merge command and this provoque a pull-requests

Thank U!

[Saxea _Flowie_]

Hi @David Martínez Labuiga ,

Interesting, can you elaborate on this? Why 1 and 2 doesn't work for you, and how an workflow with 3 would work. What would be the benefits you see?

[David Martínez Labuiga]

Hello! Yes! Thanks for responding!

I think Option 1 is the standard and fine option, but in some projects, the project administrator wants some control over the merge process.

Then there's Option 2: the developer requests a pull-request for the merge because branch-permissions that project manager has configured

However, some developers often use the command line to work; therefore, when working with many projects, it's sometimes not possible to visually tell when a project needs a web pull request.

In those cases, you're probably trying to perform a merge locally and then end up with a local branch that's out of sync with the remote branch.

Well, it can be solved with git reset --hard origin/branch and making pull requests via the web, but for some novices, this process can be complicated, and sometimes new developers or people without development experience can make mistakes that may require other actions.

So, for the project manager... I think an option to avoid this situation and add some automation to automatically avoid issues would be desirable.

I think it would be nice if there was an option to programmatically create pull requests in a limited merge situation as a branch-permissions.

Perhaps it's not 100% Attlansian's responsibility. I think the project manager could create a hook to solve this problem, but I think it would be interesting for project managers to have a configurable option they can use at their discretion for each project, especially in some projects with separate roles and groups between developers and systems technicians for these tasks and platform configuration. Those working with the cloud could also use it.

[Saxea _Flowie_]

I see, I get the general idea. I think you would need some client side hooks to implement this workflow, and possible use Bitbucket webhooks too.

We provide an app for Bitbucket cloud workflow automation. What you described is not supported out of the box, but with some customization it might be helpful to you. You might want to check it out, if you don't want to build everything from scratch, and contact us via our support if you have any questions.