Support merge request management [176686426]

Assigned

Feature Request

Status Update

No update yet.

Description

su...@staytuned.company

created issue #1

Jan 4, 2021 05:43AM

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish: Hi there,

Please provide support for merge request management in the Google source repository.

Merge request flow should be supported as follow:

Create a merge request.
Assign merge request to the user.
Give a comparison view of two branches for code review. Also, add a reviewer to the merge request for better management. Reviewer and assigner should be able to comment on the differences in collaborative work.
Maintain a history of that merge request and show the comparison of two branch
Provide option to Confirm merge, Confirm squash and merge, or Confirm rebase and merge.
Close Merge request.

If applicable, reasons why alternative solutions are not sufficient:

No alternative solution available in Google cloud source repository.

Other information (workarounds you have tried, documentation consulted, etc):

Comments

su...@google.com <su...@google.com> #2Jan 13, 2021 12:55PM

Assigned to gc...@google.com.

Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:

YourRepository > Branch > file

You have a drop down in Repository and in Branch to change anytime.

su...@staytuned.company <su...@staytuned.company> #3May 6, 2021 01:58AM

Hey! Thanks for taking a look at this. I have attached a screenshot of the home page of a Cloud Source Repository with the UI you mentioned open. You will see the main area says "No commits on the default branch." The default branch in this case is "main" (I am assuming that Cloud Source Repositories is expecting it to be "master"). As I mentioned in my original post, this is the naming system that github recommends and that they will be using by default starting 10/1/2020 (

https://github.com/github/renaming). I refer to github as an example because the repository in the screenshot is a mirror of a github repo, that has "main" as the default branch and no "master" branch.

kc...@gmail.com <kc...@gmail.com> #4Jun 17, 2021 12:28PM

Hi, this feature request has been forwarded to the Source Repository product management team so that they may evaluate it. There is no timeline or implementation guarantee for feature requests. All communication regarding this feature request is to be done here.

tu...@gtempaccount.com <tu...@gtempaccount.com> #5Oct 21, 2022 12:25PM

Using master in now discourage by a Google guideline: https://opensource.google/docs/releasing/preparing/#inclusive

But not being able to switch away from master if one wants to properly use Cloud Source Repositories is working against this policy to strictly avoid it.

gs...@gmail.com <gs...@gmail.com> #6Nov 22, 2022 10:58PM

Shouldn't this issue has a higher priority as not being able to switch away from master is working against the inclusive policy?

Issue 176686426